What problem does it solve? Coordinating sprint planning across multiple repositories is slow and inconsistent when done by hand — each repo needs its own scoped plan derived from the same PRD, and manually prompting per repo invites drift and missed scope. This Skill fans a single PRD or goal document out to every active repo in the fleet registry and produces a scoped sprint-plan.md per repo in one pass. ## Core Features & Use Cases - Parallel multi-repo drafting: Reads the fleet registry (.cto/projects.yaml), stages a per-repo prompt combining the PRD with each repo's CLAUDE.md, and drafts plans in parallel via the resolved review engine (subagent, gemini, kimi, codex, or claude-p). - Scoped, structured output: Each plan lands at the target repo's docs/sprints/sprint-NN/sprint-plan.md with required sections (Scope, Tasks, Test Plan, Acceptance Criteria, Dependencies, Risks), and repos with no applicable work are marked via a NO_SCOPE_FOR_THIS_REPO sentinel. - Dry-run and filtering: Supports --repos, --sprint, and --dry-run flags so you can preview staged plans before writing them into repos. - Use Case: A CTO with a PRD for a cross-repo feature runs the skill to get scoped sprint plans for all four dev repos at once, then reviews the synthesized summary of tasks, effort estimates, and cross-repo dependency flags. ## Quick Start Ask the agent to draft sprint plans across all active repos for the PRD at docs/prds/my-feature.md, optionally limiting to specific repos or a sprint number.
