Explanation

Understanding-oriented pages that explain why Spec Kitty works the way it does. Start here when you want the mental model behind a capability rather than step-by-step instructions.

Key pages

• Spec-driven development — the core methodology.
• Mission system — how missions and work packages relate.
• Mission-type resolution — the doctrine → charter → core seam that resolves per-mission-type behaviour.
• Execution lanes and git worktrees — the parallel execution model.
• Git workflow — what git operations the runtime owns versus the agent.
• Multi-agent orchestration — coordinating work across agents.
• Kanban workflow and runtime loop — the mission control loop.
• AI agent architecture — how supported agents integrate.
• Doctrine artifact kinds — what each of the eight doctrine artifact kinds is for.
• SPDD and the REASONS Canvas — the opt-in structured-prompt-driven-development artifact set.
• Status model and mission transition gates — how lane state is recorded and guarded.
• Event ledger writers and readers — who writes and reads each event log today, and the gaps against the event ADRs.
• Post-merge partition authority — which bytes win after consolidation, and which surface readers trust.

The full list is in the architecture index.

See also

• Tutorials — learning-oriented walkthroughs.
• How-to guides — task-oriented instructions.
• Reference — authoritative specifications.