spec-kitty.tasks

# /spec-kitty.tasks - Generate Work Packages **Version**: 0.11.0+ ## ⚠️ 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**: This is NOT the time to save tokens or rush. Take your time to: - Understand the full scope deeply - Break work into clear, manageable pieces - Write detailed, actionable guidance - Think through risks and edge cases **Token usage is EXPECTED and GOOD here**. A thorough task breakdown saves 10x the effort during implementation. Do not cut corners. --- ## 📍 WORKING DIRECTORY: Stay in the repository root checkout **IMPORTANT**: Tasks works in the repository root checkout. NO worktrees created. ```bash # Run from project root (same directory as /spec-kitty.plan): # You should already be here if you just ran /spec-kitty.plan # Creates: # - kitty-specs/<mission_slug>/tasks/WP01-*.md → In repository root checkout # - kitty-specs/<mission_slug>/tasks/WP02-*.md → In repository root checkout # (the NNN- prefix in directory listings is display-only metadata) # - Commits ALL to target branch # - NO worktrees created ``` **Do NOT cd anywhere**. Stay in the repository root checkout. **Worktrees created later**: After tasks are finalized, run your agent loop: `spec-kitty next --agent <a...