spec-kitty-mission-system

# spec-kitty-mission-system Understand how missions structure work in Spec Kitty. A mission is a domain-specific workflow blueprint that defines what phases you go through, what templates agents see, what artifacts you produce, and how to validate success. --- ## How Missions Work ### The Core Concept A mission answers: "What process should we follow to achieve this goal?" Different goals need different processes. Building a software component is different from conducting research or writing documentation. Each mission provides domain-appropriate: - **Steps** — the ordered phases of work (specify → plan → implement → review) - **Templates** — prompts that tell agents what to do at each step - **Artifacts** — expected outputs (spec.md, plan.md, tasks.md) - **Guards** — conditions that must be met before advancing (e.g., spec.md must exist before planning) - **Validation** — checks that verify the output quality - **Agent context** — personality and instructions for the AI agent ### The Hierarchy: Mission Type → Mission → Work Package → Workspace ``` Mission Type (e.g., software-dev) └── Mission (kitty-specs/042-auth-system/) ├── meta.json ← links mission to mission type + target branch ├── spec.md ← what we're building ├── plan.md ← how we'll build it ├── tasks.md ← WP breakdown └── tasks/ ├── WP01.md ← work package prompt ├── WP02.md ...