Individual skill

spk-mission-specify

Operate the Spec Kitty specify phase: turn user intent into a mission spec while preserving scope, ambiguity, and acceptance criteria.

src/charter/offering/skills/spk-mission-specify/SKILL.md

Read pinned source

Source commit 25b7cd4fbc8f42ec71219408e2b5d76e7dae38b4

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,717
Repository last updated: Nov 7, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
gemini-cli Repository topic
spec-driven-development Repository topic
cursor-agent Repository topic
github-copilot Repository topic
windsurf Repository topic
ai-coding-workflow Repository topic
ai-development-dashboard Repository topic
ai-progress-tracking Repository topic
coding-agent-orchestration Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,076 bytes

Read excerpt


# spk-mission-specify

Use this skill when creating or revising a mission specification.

## Flow

1. Run or invoke `/spec-kitty.specify` for the feature.
2. Capture the user's concrete goal, constraints, non-goals, and success
   criteria.
3. Keep unresolved product decisions explicit instead of hiding them in plan
   details.
4. If terminology matters, route to `spk-charter-glossary`.
5. If governance affects scope, route to `spk-charter-governance`.
6. When a non-trivial user flow, domain lifecycle, rule, or concept boundary is