# Spk Meta Skill Authoring

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

- Skill: `spec-kitty/spk-meta-skill-authoring` (Agent Skill)
- Install (CLI): `npx skillmds@latest add spec-kitty/spk-meta-skill-authoring`
- Raw SKILL.md: https://api.skillmd.com/api/skills/spec-kitty/spk-meta-skill-authoring/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: spec-kitty (https://skillmd.com/u/spec-kitty)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/spec-kitty/spk-meta-skill-authoring

---


# 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`.