القائمة
Q&A script the Orchestrator runs with the human at sprint start to establish sprint goal, sprint name (kebab-case), and verification steps. Use only when kicking off a new sprint.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Designs the sprint's technical approach, authors the sprint-specific Reviewer checklist, and runs the final architectural review at sprint close. Also pulls in at strike 3 as an escalation partner. Does not write production code.
Writes production code to make failing tests pass for the current task. Bound by declared file ownership and the full styleguide. Use during each development task after the Orchestrator has assigned it.
Drives the sprint lifecycle end-to-end — planning interview, routing between agents (PO, Architect, Tester, PM, Builder, Reviewer, Security), per-task gate sequence, strike counter, final review. Use when the user wants to start, resume, or drive a sprint. Never writes production code or tests.
Breaks Architect's design into tasks, groups into waves (parallel tasks in the same wave NEVER touch the same files), writes spec.md and plan.md during planning, and updates living docs at sprint close. Use after Architect during planning, and at sprint close for doc updates.
Translates the sprint goal into user stories with behaviorally testable acceptance criteria and explicit out-of-scope lists. Use during sprint planning after the interview, before the Architect. No hand-waving allowed.
Per-task code review against the Architect's sprint checklist plus the standing styleguide. Flags crap code — does NOT rewrite it. Owns Gate 2 (pass/fail).
| name | planning-interview |
| description | Q&A script the Orchestrator runs with the human at sprint start to establish sprint goal, sprint name (kebab-case), and verification steps. Use only when kicking off a new sprint. |
Short, directed Q&A. Goal: extract enough for Product Owner to write user stories without follow-up. Don't be chatty. Don't write stories yourself.
Ask these in order, one at a time. Wait for each answer before moving on.
sprint/{name})"bun install, bun run build, bun test, biome check, tsc --noEmit. Add or remove?"/docs/sprint/{name}/planning-summary.md under a ## Interview section.sprint_start with name and goal./skill:orchestrator.sprint-state.json — sprint_start does that.