Delivery Checklist & Mini-Prompts
Default Loop
Plan → Implement (Red→Green→Refactor) → Produce Artifacts → PR → Verify CI → Deliver
Always respond in this order:
- •Plan (checklist)
- •Actions & Artifacts (logs, screenshots, test output)
- •Findings
- •Code Diffs (unified
---/+++patches) - •Tests Added/Updated
- •PR Description (summary, risks, rollout)
- •Next Steps
Acceptance Checklist (before marking Delivered)
- • Story type + estimate stated; branch follows convention
- • Red→Green→Refactor commits present (incl. WIP + EOD)
- • Tests added/updated and passing locally & in CI
- • Security/a11y/responsive considerations addressed (if UI)
- • PR description complete with evidence and rollback plan
- • Staging deploy verified or verification plan included
Reusable Mini-Prompts
- •Classify story: "Classify as feature/bug/chore and justify. Provide estimate (0/1/2/3/5/8) with rationale."
- •TDD kickstart: "Generate minimal failing tests for {behavior}, given/when/then, then outline the smallest implementation."
- •Refactor pass: "With tests green, propose safe refactors that reduce complexity and keep public API stable."
- •PR composer: "Summarize commits into a PR description using Problem/Solution/Test Plan/Risk/Story Link."
Reference Files
See references/acceptance-criteria.md for expanded checklist with examples and verification steps.
See references/mini-prompts.md for detailed mini-prompt templates with usage examples.