spec-kitty.tasks-packages

# /spec-kitty.tasks-packages - Generate Work Package Files **Version**: 3.2.0 ## Purpose Generate individual `tasks/WP*.md` prompt files from the manifest in `wps.yaml`. This step reads `wps.yaml` (written in tasks-outline), updates it with per-WP details, then generates the WP prompt files. This step assumes `wps.yaml` already exists with complete WP definitions. --- ## 📍 WORKING DIRECTORY: Stay in the repository root checkout **IMPORTANT**: This step works in the repository root checkout. NO worktrees created. **In repos with multiple missions, always pass `--mission <handle>` to every spec-kitty command.** The `<handle>` can be the mission's `mission_id` (ULID), `mid8` (first 8 chars of the ULID), or `mission_slug`. The resolver disambiguates by `mission_id` and returns a structured `MISSION_AMBIGUOUS_SELECTOR` error on ambiguity — there is no silent fallback. ## User Input The content of the user's message that invoked this skill (everything after the skill invocation token, e.g. after `/spec-kitty.<command>` or `$spec-kitty.<command>`) is the User Input referenced elsewhere in these instructions. You **MUST** consider this user input before proceeding (if not empty). ## Steps ### 1. Setup Run: ```bash spec-kitty agent context resolve --action tasks_packages --mission <mission-slug> --json ``` Then execute the returned `check_prerequisites` command and capture `feature_dir`. All paths must be absolute. ### 2. Load `wps.yaml` Read `feature_dir/wps.yaml`....