Explain Spec Kitty mission types, step contracts, action indices, and when to choose each mission workflow.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Priivacy-ai/spec-kitty --skill spk-mission-types --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Spk Mission Types?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/priivacy-ai-spk-mission-types)More formats (shields.io, HTML) on the badges page.
---
name: spk-mission-types
description: "Explain Spec Kitty mission types, step contracts, action indices, and when to choose each mission workflow."
---
# spk-mission-types
Use this skill when the user asks which kind of mission to run or how mission
types differ.
## Workflow
1. Identify the requested work: software change, standalone planning,
documentation, research, or custom/team workflow.
2. Compare available mission types before creating new process.
3. Use the legacy `spec-kitty-mission-system` skill for detailed step-contract,
procedure, action-index, and template-resolution mechanics.
## Boundary
Mission types define workflow behavior. Skills explain how to operate that
behavior; they do not redefine the mission DAG.
## Built-In Types
- `software-dev`: default feature/change workflow with tasks and WP iteration.
- `research`: evidence-gathering workflow before or during product decisions.
- `plan`: planning-only workflow.
- `documentation`: documentation-oriented workflow.
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', ...
