Individual skill

spk-meta-skill-authoring

Author future Spec Kitty spk skills using the 3.2.0 naming convention, lifecycle families, and doctrine/command boundaries.

src/charter/offering/skills/spk-meta-skill-authoring/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,054 bytes

Read excerpt


# 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 `spec-kitty.<command>` slash-command files separate from
   generated `spec-kitty-<command>` command skills.
3. Preserve the older `spec-kitty-<topic>` guide skills (for example
   `spec-kitty-runtime-next`) when they remain useful aliases or detailed
   workflows. Never give a new skill a `spec-kitty-<command>` name: those
   names belong to the generated command skills.
4. Keep mission behavior in doctrine mission composition, not in skill prose.