spk-start-first-feature

Guides a first Spec Kitty feature through specify, plan, tasks, implementation, review, and merge gates.

1.6k|156|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-start-first-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spk-start-first-feature
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spk-start-first-feature
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-start-first-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New Spec Kitty users often do not know the correct order of commands and gates needed to take a feature from initial intent to a merged, reviewed change, and risk skipping review or acceptance steps.

Core Features & Use Cases

  • End-to-End Workflow Guidance: Walks through the full lifecycle: specify, plan, tasks, implementation, review, accept, merge, and retrospective.
  • Gate Enforcement: Ensures review, accept, and merge gates are not skipped even when implementation appears complete.
  • Setup Verification: Routes users to environment diagnostics when commands or skills are missing before starting.
  • Use Case: A developer installing Spec Kitty for the first time wants to ship their first feature; this Skill sequences every command from /spec-kitty.specify through the final retrospective.

Quick Start

Ask the assistant to walk you through starting your first Spec Kitty feature from setup through merge and retrospective.

Frequently Asked Questions about spk-start-first-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start my first feature with Spec Kitty?

Start by verifying your setup, then create a mission with /spec-kitty.specify, build a plan with /spec-kitty.plan, and generate work packages with /spec-kitty.tasks. Then advance implementation, review, accept, and merge in order.

What is the Spec Kitty workflow order for a new feature?

The order is specify, plan, tasks, implementation, review, accept, merge, then mission review and retrospective. Each stage produces repository-native artifacts that feed the next step.

Can I skip the review or accept gates in Spec Kitty?

No. Review, accept, and merge gates must not be skipped even when implementation appears complete, because they preserve the audit trail and quality controls that Spec Kitty is built around.

What should I do if Spec Kitty commands or skills are missing?

Run the setup diagnostics skill first to verify the installation and agent surface. Missing commands or skills indicate an incomplete install that must be fixed before starting a mission.

When is Spec Kitty not the right tool for a task?

Spec Kitty is overkill for one-off edits, tiny scripts, or teams that do not use Git. It is designed for repeatable spec-driven development with work packages, parallel agents, and review gates.