spec-kitty.tasks-packages

To generate task prompt files from a YAML work manifest, this Skill reads your existing wps.yaml definitions and materializes them into flat feature_dir/tasks/WP*.md files with required YAML frontmatter. It automates prompt generation directly from the manifest entries.

Automating work package prompt creation for spec-kitty involves reading complete WP definitions from wps.yaml and outputting flat tasks/WP*.md files. The process populates owned_files, requirement_refs, subtasks, and prompt_file fields automatically.

Generating prompt files from wps.yaml does not alter existing dependency values. The process preserves any pre-existing authoritative dependencies in your wps.yaml manifest while adding metadata fields like owned_files and prompt_file to the entries.

You cannot organize generated work package task files into status subfolders. The execution planning enforces a strict flat tasks/ directory structure, producing files like WP*.md directly under feature_dir/tasks without any nested status folders.

You need a complete work manifest in wps.yaml before generating WP task prompts. The Skill requires existing complete WP definitions for a specified mission context to properly materialize the owned files and prompt files without altering dependencies.