Operate documentation-oriented Spec Kitty missions and ensure docs stay tied to shipped behavior and doctrine.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add Priivacy-ai/spec-kitty --skill spk-mission-documentation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Spk Mission Documentation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/priivacy-ai-spk-mission-documentation)More formats (shields.io, HTML) on the badges page.
---
name: spk-mission-documentation
description: "Operate documentation-oriented Spec Kitty missions and ensure docs stay tied to shipped behavior and doctrine."
---
# spk-mission-documentation
Use this skill when the mission is primarily documentation, release notes,
guides, or user-facing explanation.
## Flow
1. Confirm whether this is a documentation mission or a software mission with
docs as acceptance criteria.
2. Ground docs in current product behavior, not intended future behavior unless
clearly marked.
3. Cross-check terms with `spk-doctrine-glossary`.
4. If docs describe commands or workflows, cross-check `spk-start-command-map`.
## Completion Standard
Documentation should make the next user action obvious and should not create a
second source of truth for runtime behavior.
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', ...