Deliver one user-visible capability with explicit acceptance examples and negative cases. Keep schema, interface, and UI changes reviewable. Check authorization, PII, rate limits, accessibility, and backward compatibility.
Objective
deliver one user-visible capability.
Context
product requirement, API contract, design, existing patterns.
Decompose
plan, data and interface changes, implementation, tests, docs, preview.
Criteria
acceptance examples and negative cases pass; backward compatibility stated.
Files/tools
explicit allowlist plus generated file list; repository tools only.
Review/security
review permissions, PII, rate limits, accessibility.
Commit/rollback
separate schema, code, and UI commits only if rollback requires it; migration has a down or restore plan.
Output
diff, screenshots or API evidence, test report.
Handoff checklist
- Acceptance examples and negative cases
- Named files and allowed tools
- Security and accessibility review
- Preview or API evidence attached
Editorial recipe adapted from the project’s September 2026 research brief. Commands, authority and acceptance tests must be matched to your repository. No production execution is implied.