spec-kitty.tasks-outline

# /spec-kitty.tasks-outline - Create Work Package Manifest **Version**: 3.2.0 ## Purpose Create `wps.yaml` — the structured work package manifest that defines WP metadata, dependencies, and file ownership. `tasks.md` is generated automatically from this manifest by `finalize-tasks`. > ⚠️ DO NOT write `tasks.md`. The system generates it from `wps.yaml`. Writing > `tasks.md` manually will have it overwritten by `finalize-tasks`. ## ⚠️ CRITICAL: THIS IS THE MOST IMPORTANT PLANNING WORK **You are creating the blueprint for implementation**. The quality of work packages determines: - How easily agents can implement the feature - How parallelizable the work is - How reviewable the code will be - Whether the feature succeeds or fails **QUALITY OVER SPEED**: Take your time to understand the full scope deeply, break work into clear pieces, and write detailed guidance. --- ## 📍 WORKING DIRECTORY: Stay in the repository root checkout **IMPORTANT**: This step works in the repository root checkout. NO worktrees created. **Do NOT cd anywhere**. Stay in the repository root checkout. **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 me...