Map Spec Kitty slash commands and CLI entry points to spk skills. Use when choosing /spec-kitty.* commands or explaining command-skill boundaries.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Priivacy-ai/spec-kitty --skill spk-start-command-map --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Spk Start Command Map?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/priivacy-ai-spk-start-command-map)More formats (shields.io, HTML) on the badges page.
---
name: spk-start-command-map
description: "Map Spec Kitty slash commands and CLI entry points to spk skills. Use when choosing /spec-kitty.* commands or explaining command-skill boundaries."
---
# spk-start-command-map
Route command questions without conflating command wrappers and operating
skills.
## Flow
1. Read `references/command-map.md`.
2. Choose the command for execution and the `spk-*` skill for operating
guidance.
3. If the user asks for discovery rather than a command, route to
`spk-meta-skill-map`.
## Boundary
`/spec-kitty.*` files are generated slash-command or prompt-command surfaces.
`spec-kitty.<command>` Agent Skills are generated under `.agents/skills/` for
skill-native hosts. `spk-*` skills are user-facing operating guides. Keep the
surfaces distinct: dotted names are executable command surfaces; hierarchical
`spk-*` names are operating guidance.
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', ...
