OpenParable
Skip to content
← Back to skills

Spk Start First Feature

Productivity
spk-start-first-feature

Spk Start First Feature is an Agent Skill for productivity published in the Priivacy-ai/spec-kitty repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Priivacy-ai/spec-kitty/blob/HEAD/src/doctrine/skills/spk-start-first-feature/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/spk-start-first-feature, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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.