spec-kitty

How to Generate Work Packages

Use this guide to turn a plan into work packages with /spec-kitty.tasks.

Prerequisites

• kitty-specs/<feature>/plan.md exists
• All [NEEDS CLARIFICATION] items are resolved

The Command

In your agent:

/spec-kitty.tasks

What Gets Created

• kitty-specs/<feature>/tasks.md (overview checklist)
• kitty-specs/<feature>/tasks/WP01-*.md, WP02-*.md, … (prompt files)

Work packages live in a flat tasks/ directory. Lane status is stored in each prompt file frontmatter via lane: "planned".

Understanding Work Packages

Each WP file contains:

• A single goal for the agent
• Subtasks and dependencies
• The exact completion command to move the WP to review

Finalizing Tasks

After reviewing the generated WPs, finalize the task set.

In your terminal:

spec-kitty agent feature finalize-tasks

Example Output

kitty-specs/012-feature/tasks.md
kitty-specs/012-feature/tasks/WP01-auth-backend.md
kitty-specs/012-feature/tasks/WP02-auth-ui.md
kitty-specs/012-feature/tasks/WP03-tests.md

Troubleshooting

• Missing plan: Run /spec-kitty.plan first.
• Tasks look incomplete: Resolve clarifications in plan.md and rerun /spec-kitty.tasks.
• Wrong directory: Run from the main repository root.

---

Command Reference

• Slash Commands - All /spec-kitty.* commands
• Agent Subcommands - finalize-tasks and more
• File Structure - Where tasks are stored

See Also

• Create a Plan - Required before task generation
• Implement a Work Package - Next step after tasks
• Handle Dependencies - Managing WP dependencies

Background

• Kanban Workflow - Lane transitions explained
• Workspace-per-WP Model - Why one workspace per WP

Getting Started

• Your First Feature - Complete workflow walkthrough

This site is open source. Improve this page.