skills.rest
Priivacy-ai
Priivacy-aiOFFICIAL
Explore all skills by this author →
GitHub

spk-mission-documentation

Guides documentation missions in Spec Kitty to keep docs aligned with shipped behavior.

1.6k|156|Updated Oct 9, 2025
Search Tags:#glossary#release notes#user guides#Technical Writing#Documentation#spec-kitty
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-mission-documentation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spk-mission-documentation
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spk-mission-documentation
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-mission-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation missions often drift away from actual product behavior, creating a second source of truth that confuses users. This Skill keeps Spec Kitty documentation work grounded in what the product actually does today.

Core Features & Use Cases

  • Mission Classification: Confirms whether the work is a pure documentation mission or a software mission where docs are acceptance criteria.
  • Behavior Grounding: Ensures docs describe current product behavior, marking future behavior explicitly when mentioned.
  • Terminology Consistency: Cross-checks wording against the doctrine glossary and command map so docs match canonical terms and workflows.
  • Use Case: When writing release notes or user guides for a Spec Kitty feature, use this Skill to verify every command reference matches the actual CLI and every term matches the project glossary.

Quick Start

Ask the agent to run a documentation mission for the new feature and verify the guide against current CLI behavior and the doctrine glossary.

Frequently Asked Questions about spk-mission-documentation

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

FAQPage Schema
How do I run a documentation mission in Spec Kitty?▼

Start by confirming whether the work is a pure documentation mission or a software mission with docs as acceptance criteria. Then ground all content in current product behavior and cross-check terms against the doctrine glossary before completion.

How do I keep Spec Kitty docs consistent with CLI commands?▼

Cross-check every command or workflow reference in the docs against the spk-start-command-map skill. This ensures documented commands match the actual CLI surface rather than intended or outdated behavior.

Can documentation describe features that are not shipped yet?▼

Docs should describe current product behavior by default. Future or intended behavior may be included only when clearly marked as such, so readers are not misled about what works today.

What is the completion standard for Spec Kitty documentation?▼

Documentation is complete when the next user action is obvious and the docs do not create a second source of truth for runtime behavior. Terminology must match the doctrine glossary.

When should I not use a documentation-only mission?▼

Avoid a docs-only mission when the work changes runtime behavior, since docs then become acceptance criteria of a software mission. Pure documentation missions fit guides, release notes, and user-facing explanations.

Related Skills

Explore More Content & Communication Skills→
gr8routdoorsgr8routdoors

shape-spec

Shape scope, design, and acceptance criteria for new work in plan mode.

Community
Advanced
compozycompozy
182

ship-pr

Generate documentation impact notes, release notes, and a GitHub PR description, then commit and open the PR.

Official
Advanced
GainInsightDevGainInsightDev

af-enforce-glossary

Validate domain terminology in BDD scenarios against a canonical glossary.

Official
Basic
semaphoreuisemaphoreui
14.1k

semaphore-cli-docs

Generate and synchronize CLI documentation pages from Cobra command code.

Official
Advanced