spk-mission-plan

Convert a completed spec into architecture, data flow, risks, and implementation strategy.

1.6k|156|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-mission-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spk-mission-plan
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spk-mission-plan
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-mission-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about spk-mission-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an implementation plan from a spec in Spec Kitty?

Run the plan phase by invoking /spec-kitty.plan against the active mission. The plan is grounded in the spec and existing repo architecture, and it makes tradeoffs explicit across interfaces, data flow, migrations, tests, rollout, and risks.

What should a spec-driven implementation plan include?

A plan should cover architecture, data flow, interfaces, migration needs, test strategy, rollout approach, and identified risks. For non-trivial architecture or risky interactions, diagrams should be used where they reduce prose.

What happens if the plan phase finds a problem in the spec?

The plan must not silently change functional requirements. When planning uncovers a spec issue, the workflow returns to the specify phase (spk-mission-specify) so the spec is corrected before planning continues.

When should I use diagrams in an implementation plan?

Use diagrams for non-trivial architecture, data or control flow, component boundaries, migrations, or risky interactions. The skill loads spk-doctrine-show-me and adds diagrams only where they materially reduce prose.

Where do research gaps go during the plan phase?

Research gaps discovered while planning are routed to spk-mission-research, and unclear mission type or workflow questions are routed to spk-mission-types, keeping the plan focused on implementation strategy.