By 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
- Confirm whether this is a documentation mission or a software mission with docs as acceptance criteria.
- Ground docs in current product behavior, not intended future behavior unless clearly marked.
- Cross-check terms with
spk-doctrine-glossary. - 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.