writing-sprint-prompts

Drafting sprint prompts for Claude Code workflows involves creating a PROMPT.md file that captures phase, sprint, issue, and branch context. This file must include explicit acceptance criteria, file scopes, testing plans, Codex delegability analysis, and deployment references for implementers.

A sprint PROMPT.md for GitHub-backed branching should include explicit acceptance criteria, files to touch, testing plans, Codex delegability analysis, deployment references, and self-review checklists. It also requires phase, sprint, issue, and branch context to ensure clear handoffs.

Yes, sprint prompts support Codex delegation by requiring a delegability analysis within the PROMPT.md. This analysis helps Phase Leads determine which tasks can be delegated to Codex during multi-phase software projects.

Refining sprint prompts after Sprint 0 involves incorporating friction findings and UX review results into subsequent prompts. This process sharpens later sprint prompts by updating acceptance criteria, testing plans, and execution guidance based on early sprint feedback.

The best way to structure acceptance criteria in sprint prompts is to state them explicitly within the PROMPT.md alongside file scopes and testing plans. This ensures implementers know exactly what to build, test, and review before a sprint can be considered complete.

Yes, this sprint prompt drafting approach works without external dependencies. It operates as a standalone method for Phase Leads to turn project context into ready-to-use prompts, requiring only project context, acceptance criteria, and deployment guidance as inputs.