/spk-meta-skill-authoring
Author future Spec Kitty spk skills using the 3.2.0 naming convention, lifecycle families, and doctrine/command boundaries.
$ npx -y skills add Priivacy-ai/spec-kitty --skill spk-meta-skill-authoring --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/spk-meta-skill-authoring
Context preview
The summary Claude sees to decide when to auto-load this skill.
Author future Spec Kitty spk skills using the 3.2.0 naming convention, lifecycle families, and doctrine/command boundaries.
SKILL.md
spk-meta-skill-authoring.SKILL.mdname: spk-meta-skill-authoring description: "Author future Spec Kitty spk skills using the 3.2.0 naming convention, lifecycle families, and doctrine/command boundaries."
spk-meta-skill-authoring
Use this skill when creating or revising a Spec Kitty skill.
Rules
1. Name public operating skills `spk-<family>-<action-or-topic>`. 2. Keep generated slash-command files separate from generated `spec-kitty.<command>` Agent Skills. 3. Preserve legacy `spec-kitty-*` skills when they remain useful aliases or detailed workflows. 4. Keep mission behavior in doctrine mission composition, not in skill prose. 5. Add tests when changing the public skill inventory.
Families
Use only established families unless a new family improves discovery: `start`, `mission`, `run`, `gate`, `admin`, `team`, `doctrine`, `integrate`, or `meta`.
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
Other skills on spec-kitty.
- /ad-hoc-profile-load
Legacy alias for resolver-backed profile loading. Use the canonical spk-doctrine-profile-load skill for identity, boundaries, and governance. Triggers: "act as the architect", "load the reviewer profile", "switch to researcher", "use the planner role", "adopt a profile".
Open skill - /adversarial-squad
Deploy a bounded, profile-loaded adversarial review squad at an SDD point-cut (post-spec, post-plan, post-tasks, pre-merge, or an ad-hoc decision) so independent doctrine lenses converge on findings one reviewer would miss. Triggers: "deploy a squad", "adversarial squad",
Open skill - /spec-kitty-bulk-edit-classification
Recognize when a mission is a bulk edit and drive the occurrence-classification guardrail on the user's behalf. Triggers: user says any variant of "rename X to Y", "change the terminology", "migrate all occurrences", "replace across the codebase", "the X feature is now the Y
Open skill - /spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers:
Open skill - /spec-kitty-git-workflow
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management",
Open skill - /spec-kitty-glossary-context
Curate and apply canonical terminology across Spec Kitty missions. Triggers: "update the glossary", "use canonical terms", "check terminology", "add a term", "fix term drift", "glossary conflicts", "resolve ambiguity", "review terminology consistency". Does NOT handle: runtime
Open skill