adversarial-squad
Deploy a bounded, profile-loaded adversarial review squad at a mission point-cut so independent doctrine lenses converge on…
@spec-kittyInstall SkillAgent Orchestration
Skill
/spk-meta-skill-authoring
Author future Spec Kitty spk skills using the 3.2.0 naming convention, lifecycle families, and doctrine/command boundaries.
Claude Code
$ npx -y skills add spec-kitty/spec-kitty --skill spk-meta-skill-authoring --agent claude-code
Codex
$ npx skills add spec-kitty/spec-kitty --skill spk-meta-skill-authoring -a codex -y
Cursor
$ npx skills add spec-kitty/spec-kitty --skill spk-meta-skill-authoring -a cursor -y
Gemini CLI
$ npx skills add spec-kitty/spec-kitty --skill spk-meta-skill-authoring -a gemini-cli -y
GitHub Copilot
$ npx skills add spec-kitty/spec-kitty --skill spk-meta-skill-authoring -a github-copilot -y
OpenCode
$ npx skills add spec-kitty/spec-kitty --skill spk-meta-skill-authoring -a opencode -y
Windsurf
$ npx skills add spec-kitty/spec-kitty --skill spk-meta-skill-authoring -a windsurf -y
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 `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. 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`, `charter`, `practice`, `integrate`, or `meta`.
Ships withspec-kitty
Spec-Driven Development with organizational governance. Specs tell AI agents what to build; Charter governs how they build it. Git-native missions, enforceable workflows, and consistent engineering standards across AI coding agents and harnesses.
1.7k45 skills
Stars on GitHub
Momentum
- stars in total
- 1.7k
Other skills on spec-kitty.
@spec-kittyInstall Skillspec-kitty-git-workflo…
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree…
@spec-kittyInstall Skillspec-kitty-implement-r…
Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state…
@spec-kittyInstall Skillspec-kitty-mission-rev…
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift,…
@spec-kittyInstall Skillspec-kitty-mission-sys…
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action…
@spec-kittyInstall Skillspec-kitty-orchestrato…
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI. Triggers:…
@spec-kittyInstall SkillMore skills from other plugins.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by…
@paperclipaiInstall Skilladr-create
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
@ruvnetInstall SkillQuestions about spk-meta-skill-authoring.
- Which coding agents can use spk-meta-skill-authoring?
- spk-meta-skill-authoring installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.