What problem does it solve? Turning an approved design into concrete, ordered implementation work is error-prone: tasks end up vague, unordered, or missing test coverage. This Skill converts a change's proposal, specs, and design into a structured tasks.md checklist with dependency-ordered phases. ## Core Features & Use Cases - Phased Task Breakdown: Organizes work into Foundation, Core Implementation, Integration, Testing, and Cleanup phases with hierarchical numbering (1.1, 1.2, 2.1). - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, writing tasks.md to openspec/changes/{change-name}/ or persisting to Engram memory. - Quality Rules Enforcement: Requires every task to be specific, actionable, verifiable, and small, with a 530-word size budget and TDD red-green-refactor support. - Use Case: After a design document is approved for a new authentication feature, the orchestrator launches this Skill to produce a tasks.md listing each file to create, each test to write, and the exact implementation order. ## Quick Start Ask the orchestrator to create the task breakdown for your change, providing the change name and artifact store mode so it can read the proposal, specs, and design and produce tasks.md.
