How to Create a Technical Plan

Use this guide to turn a finished spec into a technical plan with /spec-kitty.plan.

Prerequisites

• kitty-specs/<feature>/spec.md exists
• You are in the repository root checkout
• Planning artifacts stay on the mission's target branch (current branch by default, or an explicit --target-branch)

The Command

In your agent:

/spec-kitty.plan

Optionally include your stack or architecture preferences in the same message.

The Planning Interview

The planner asks architecture and non-functional questions. It pauses with WAITING_FOR_PLANNING_INPUT until you answer each one.

What Gets Created

• kitty-specs/<feature>/plan.md
• kitty-specs/<feature>/research.md (if research is required)
• kitty-specs/<feature>/data-model.md (when data is involved)
• kitty-specs/<feature>/contracts/ (API contracts when applicable)
• Updated agent context files (based on the plan)

Example

/spec-kitty.plan Use FastAPI + PostgreSQL. Deploy on Fly.io. Use JWTs for auth.

Troubleshooting

• No plan generated: Make sure the spec exists and you are running in the repository root checkout.
• Planner keeps asking questions: Provide the missing architectural details; the plan will not generate until the interview is complete.
• Planner is targeting the wrong branch: Resolve branch intent first with spec-kitty agent mission branch-context --json or recreate the mission with the right --target-branch.
• Need to update the plan: Re-run /spec-kitty.plan with the new constraints.

---

Command Reference

• Slash Commands - All /spec-kitty.* commands
• CLI Commands - Full CLI reference
• File Structure - Where plans are stored

See Also

• Create a Specification - Required before planning
• Keep Main Clean - Choose a target branch without changing planning location
• Generate Tasks - Next step after planning

Background

• Spec-Driven Development - The philosophy
• Kanban Workflow - How work flows after planning

Getting Started

• Your First Feature - Complete workflow walkthrough