spec-kitty-tasks

Generating work packages from a feature plan involves parsing your design and plan documents to create cohesive work packages and per-WP prompts. This enables end-to-end task execution by deriving dependencies and validating references against your plan.

Automate task planning by running a single command to process your feature plan into a flat tasks.md file. This derives work packages and subtasks, produces independent prompt files with frontmatter metadata, and prepares them for commit to your target branch.

Work package prompts include YAML frontmatter metadata like execution_mode, owned_files, and authoritative_surface. This metadata supports requirement mapping and finalization workflows to ensure governance and traceability across all work packages.

Yes, you can validate task dependencies by mapping them against your spec.md and plan.md documents. The process checks references, enforces YAML frontmatter requirements, and ensures all work package dependencies are correctly derived before finalization.

Generated task prompts use a flat directory structure with YAML frontmatter metadata for orchestration. Each work package receives an independent prompt file in the tasks/ directory, alongside a master tasks.md file that coordinates the execution workflow.

Finalization before commit ensures requirement mapping accuracy and validates all work package references against your plan documents. This step enforces governance and traceability across work packages, preventing incomplete or misaligned task definitions from entering your branch.