What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is slow and error-prone. This Skill automates that step by reading your spec-kit design artifacts and producing a structured tasks.md where every task is specific enough to execute without extra context. ## Core Features & Use Cases - Design-driven task generation: Reads plan.md, spec.md, and optional data-model.md, contracts/, research.md, and quickstart.md to build tasks grounded in your actual design. - User-story organization: Groups tasks into phases per user story (P1, P2, P3...) with dependency graphs, parallel execution markers, and independent test criteria so each story can ship on its own. - Strict checklist format: Enforces a consistent format (checkbox, task ID, [P] parallel marker, [USn] story label, exact file path) and validates completeness before reporting. - Extension hooks: Supports optional and mandatory before/after hooks declared in .specify/extensions.yml. - Use Case: After writing a spec and plan for a new checkout feature, run this Skill to get a tasks.md with setup, foundational, per-story, and polish phases, plus a suggested MVP scope limited to User Story 1. ## Quick Start Ask the assistant to generate the tasks.md for the current feature from the spec and plan in the .specify directory.
