Operate the Spec Kitty plan phase: convert a completed spec into architecture, data flow, risks, and implementation strategy.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add Priivacy-ai/spec-kitty --skill spk-mission-plan --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Spk Mission Plan?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/priivacy-ai-spk-mission-plan)More formats (shields.io, HTML) on the badges page.
---
name: spk-mission-plan
description: "Operate the Spec Kitty plan phase: convert a completed spec into architecture, data flow, risks, and implementation strategy."
---
# spk-mission-plan
Use this skill when a mission has a spec and needs an implementation plan.
## Flow
1. Invoke `/spec-kitty.plan` against the active mission.
2. Ground the plan in the spec and existing repo architecture.
3. Make tradeoffs explicit: interfaces, data flow, migration needs, tests,
rollout, and risks.
4. Route research gaps to `spk-mission-research`.
5. Route unclear mission type or workflow questions to `spk-mission-types`.
6. For non-trivial architecture, data/control flow, boundaries, migrations, or
risky interactions, load `spk-doctrine-show-me` and use diagrams where they
materially reduce prose.
## Guardrail
Do not let the plan silently change functional requirements. If the plan
discovers a spec issue, return to `spk-mission-specify`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...