spec-kitty-tasks-packages

To generate work-packages from a markdown task list, this Skill parses tasks.md and outputs flat WP prompt files in feature_dir/tasks/WP*.md with frontmatter for dependencies and execution mode. It updates tasks.md to reference the new prompt files for traceability.

A work-package prompt file is a ready-to-implement markdown document containing frontmatter for owned_files, authoritative_surface, and execution_mode. You need work-packages when converting high-level task outlines into executable units to ensure consistent planning across teams.

You automate creating work-package files by running the spec-kitty tasks-packages workflow from the project root. It reads tasks.md and automatically generates WP*.md files containing frontmatter with dependencies, owned_files, authoritative_surface, and execution_mode fields.

Yes, flat work-package prompts support software engineering workflow automation by creating standardized WP templates in a single feature_dir/tasks/ directory, enabling repeatable planning workflows across multiple features.

You need a tasks.md file in your project root to generate flat WP prompts. The workflow places the generated WP*.md files directly into the feature_dir/tasks/ directory and updates the original tasks.md to link back to them.

Your tasks.md file needs to reference generated work-package prompt files to maintain auto-linking and traceability. This integration ensures updates to tasks.md reflect in the WP references and connects with spec-kitty's planning and implement steps.