Skip to content
Development
Skill

/spk-start-first-feature

Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective.

From plugin
spec-kitty
1.5k53 skills1 command
Install
$ npx -y skills add Priivacy-ai/spec-kitty --skill spk-start-first-feature --agent claude-code

How 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-start-first-feature

Context preview

The summary Claude sees to decide when to auto-load this skill.

Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective.

SKILL.md

spk-start-first-feature.SKILL.md
name: spk-start-first-feature
description: "Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective."

spk-start-first-feature

Use this skill when a user wants to start their first Spec Kitty mission or feature and needs the end-to-end path.

Workflow

1. Verify install and agent surface with `spk-admin-setup-doctor` if commands or skills are missing. 2. Create or select the mission with `/spec-kitty.specify`. 3. Build the plan with `/spec-kitty.plan`. 4. Produce work packages with `/spec-kitty.tasks` or the outline/packages/finalize split when the project uses staged task authoring. 5. Advance work with `spk-run-next`. 6. Drive implementation/review loops with `spk-run-implement-review`. 7. Close with `spk-gate-accept`, then `spk-gate-merge`. 8. Finish post-merge checks with `spk-gate-mission-review` and `spk-gate-retrospective`.

Guardrails

  • Keep the user on one mission until a blocker requires a different route.
  • Treat generated runtime prompt files as authoritative for the current action.
  • Do not skip review, accept, or merge gates just because implementation appears

complete.

Ships withspec-kitty

Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.

Get the whole plugin

Other skills on spec-kitty.