---
name: bespoke-quality-workflow
description: Guide production software work through repository intake, bounded planning, implementation, review, verification, and truthful handoff. Use when a request changes a product, codebase, release process, or public capability and needs evidence-backed delivery.
---

# Bespoke Quality Workflow

## Run the delivery loop

1. Inspect the repository, instructions, branch, dirty files, and relevant execution path before proposing changes.
2. Convert requirements into a plan with explicit files, behavioural tests, checkpoints, and verification evidence.
3. Implement one reviewable unit at a time. Write the behaviour test first and observe its intended failure.
4. Diagnose every failing check from its error and data flow before changing source.
5. Review the result for catalogue drift, false recovery states, inaccessible interaction, unsafe boundaries, and unsupported claims.
6. Run fresh, full checks before a checkpoint, commit, or completion statement.
7. Hand off the outcome, evidence, limits, deployment boundary, and not-done work in plain language.

## Keep boundaries truthful

- Preserve unrelated user changes and stop if the requested work would overwrite them.
- Do not deploy, publish, merge, create secrets, alter DNS, or make external writes without explicit authority.
- Do not replace missing evidence with optimistic wording. State what was and was not verified.