requirements-sprint

name	requirements-sprint
description	Requirements Sprint ceremony. Spawns a single Developer to elicit requirements from the user through natural language dialogue, producing a requirements document and initial Product Backlog.
disable-model-invocation	false

Inputs

• state.json → phase: "new" or "requirements_sprint"

Outputs

• docs/requirements.md — business, functional, non-functional requirements (committed to repo)
• CLAUDE.md — project root, ~200 lines target (project overview + cautions). Created if missing; existing→user choice
• state.json → new→requirements_sprint→backlog_created
• backlog.json — initial coarse-grained PBIs + next_pbi_id

Preconditions

• state.json phase: "new" or "requirements_sprint"
• No existing requirements.md (new) or incomplete (resume)

Roles

• Scrum Master — state.json transitions (steps 1, 9), Developer lifecycle (step 2 spawn, step 9 terminate), backlog.json initialization (step 6), user confirmation prompts (steps 7, 8a).
• Developer (Requirements interviewer) — user dialogue (steps 3, 4), docs/requirements.md authoring (step 5), CLAUDE.md authoring when overwrite/append chosen (step 8b).

Steps

1. Update state.json → phase: "requirements_sprint":

   .scrum/scripts/update-state-phase.sh requirements_sprint
   

2. Spawn 1 Developer for requirements interview
3. Developer engages user in natural language:
   • Business: problem, users, goals
   • Functional: features, key workflows
   • Non-functional: performance, security, scalability, platform constraints
   • Constraints: tech preferences, limitations
4. Unclear/incomplete→follow-up questions. Do not proceed until sufficiently clear
5. Produce docs/requirements.md with structured sections (create docs/ dir if missing)
6. SM creates backlog.json: coarse PBIs (status: "draft"), set next_pbi_id, set product_goal
7. Present requirements summary + initial backlog→user confirmation
8. CLAUDE.md initialization (project root):
   • Exists→ask user: overwrite / append / skip
   • Not exists or user chose overwrite/append→Developer writes/updates CLAUDE.md:
     • Project overview: purpose, users, key features (from requirements.md)
     • Cautions level only: key constraints, security concerns, critical conventions. No detailed architecture/directory structure (Integration Sprint regenerates that)
     • Target ~200 lines (目安). Exceeded→warn user, do not block
9. Update state.json → phase: "backlog_created":

   .scrum/scripts/update-state-phase.sh backlog_created
   

   Then terminate Requirements Sprint Developer.

Ref: FR-002

Exit Criteria

• requirements.md exists (business + functional + non-functional covered)
• backlog.json exists (≥1 draft PBI)
• CLAUDE.md exists at project root (created or user-confirmed skip/append)
• state.json phase: "backlog_created"
• User confirmed