What problem does it solve? Turning a finished tech design into actionable development work is error-prone: slices that are too coarse hide multi-week work behind one issue, while slices that are too fine drown the tracker in trivia. This Skill enforces a disciplined slicing process with hard preconditions so implementation planning only happens against a complete, reviewed design. ## Core Features & Use Cases - Gate enforcement: Refuses to run unless the tech design is reviewed, all gap issues are closed, and every component in the inventory has a design doc on disk. - Dependency-ordered task slicing: Walks each component design, proposes PR-sized tasks with acceptance criteria and design sources (ADRs/TRs), and mirrors the list back for explicit approval before filing anything. - GitHub issue filing: Creates one story(impl): issue per task via gh issue create, wires ordering with typed blocked by edges, and places issues on the project board with milestone and Area fields. - Use Case: After finishing the tech design and all component designs for a self-hosted media storage capability, ask to plan implementation and receive a confirmed, dependency-ordered manifest of GitHub issues ready for per-task development. ## Quick Start Ask the assistant to plan implementation for your capability, for example: plan implementation for self-hosted-personal-media-storage and file the issues once I approve the task list.
