What problem does it solve?
Teams using spec-driven development often jump from a written spec straight into coding, losing architectural decisions, tradeoffs, and risk analysis along the way. This Skill runs the Spec Kitty plan phase so every mission produces an explicit implementation plan grounded in the spec and the existing repository architecture.
Core Features & Use Cases
- Plan Generation: Invokes
/spec-kitty.plan against the active mission to produce architecture, data flow, and implementation strategy from a completed spec.
- Explicit Tradeoffs: Documents interfaces, migration needs, tests, rollout, and risks so reviewers can evaluate decisions before code is written.
- Workflow Routing: Sends research gaps to
spk-mission-research, workflow questions to spk-mission-types, and spec defects back to spk-mission-specify.
- Use Case: After finalizing a feature spec in a Spec Kitty mission, run this Skill to produce a plan that maps components, data flow, and risky interactions, with diagrams for non-trivial architecture via
spk-doctrine-show-me.
Quick Start
Ask the agent to run the Spec Kitty plan phase for the active mission and turn the current spec into an implementation plan with architecture, risks, and rollout strategy.