What problem does it solve?
When working with Spec Kitty, users face three overlapping surfaces: generated /spec-kitty.* slash commands, generated spec-kitty.<command> Agent Skills under .agents/skills/, and user-facing spk-* operating skills. This Skill removes the confusion of choosing the right entry point by routing each user intent to the correct command and its matching operating skill.
Core Features & Use Cases
- Command-to-skill routing: Reads a reference table that maps user intents (specify, plan, tasks, implement, review, accept, merge, dashboard, charter) to the correct slash command and
spk-* skill.
- Surface boundary enforcement: Keeps dotted executable command surfaces distinct from hierarchical
spk-* operating guidance so wrappers and skills are never conflated.
- Discovery fallback: Redirects pure discovery questions to
spk-meta-skill-map instead of guessing a command.
- Use Case: A user asks which command reviews a work package; the Skill routes them to
/spec-kitty.review for execution and spk-run-review-wp for operating guidance.
Quick Start
Ask which Spec Kitty command or skill to use for your current task, such as creating a plan or reviewing a work package.