What problem does it solve? Turning an approved task specification and architecture into concrete, executable development work is error-prone: tasks get invented without traceability, acceptance criteria get lost, and developers end up re-designing architecture mid-implementation. This Skill produces a structured plan where every task traces back to the spec. ## Core Features & Use Cases - Top-down planning: First tasks create stub implementations wired into the main flow with an end-to-end test, so the whole system runs from the start; later tasks replace stubs with real logic. - Traceability coverage table: Every unit of the task_spec maps to at least one task, and acceptance criteria are explicitly bound to the tasks that prove them. - Concrete task definitions: Exact file paths, class and method names with parameters and types, plus e2e, unit, and regression test expectations — no code, no vague descriptions. - Use Case: After an architecture review passes, ask for a development plan and receive a sequenced task list with a coverage table, per-task test strategy, and open questions, ready to hand to implementation. ## Quick Start Use the task-planning skill to break down the approved task_spec and architecture into an ordered development plan with tests for each task.
