spec-kitty.specify

Creates mission specifications from user intent via guided discovery and branch checks.

Updated May 13, 2026
One-click install
npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-specify-kimprobably
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-kitty.specify
Source: https://github.com/kimprobably/maestro-os/tree/main/.agents/skills/spec-kitty.specify
Command: npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-specify-kimprobably

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams turn an initial idea into a complete, testable mission specification that can be planned and implemented reliably, reducing rework caused by missing requirements or ambiguous scope.

Core Features & Use Cases

  • Guided discovery to lock scope: Runs a structured discovery interview and blocks progress until intent, constraints, and success outcomes are clear.
  • Branch-contract safety checks: Confirms the current branch, planning/base branch, merge target branch, and whether they match the intended landing branch before creating the mission.
  • Creates mission artifacts in-repo: Generates a spec.md and meta.json in the correct feature directory and validates readiness with a requirements checklist.
  • Use Case: When you want to add a new product capability, you can specify the feature at a high level and get a complete requirements spec ready for planning and implementation.

Quick Start

Run /spec-kitty.specify with your feature idea, then answer the discovery question(s) to produce a mission specification draft ready for planning.

Frequently Asked Questions about spec-kitty.specify

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

FAQPage Schema
How do I generate a requirements spec with measurable success criteria for a new feature?

To generate a requirements spec, you run a guided discovery interview that captures intent, constraints, and success outcomes, then formats functional and non-functional requirements with strict, measurable success criteria and testing scenarios.

How do I create planning artifacts in-repo without using worktrees for a research project?

You create in-repo planning artifacts by generating a spec.md and meta.json directly in the correct feature directory, enforcing branch contract confirmation without requiring isolated worktrees.

What is a branch strategy discovery check and when do I need it for mission specification?

Branch strategy discovery is a safety check that confirms your current, planning, base, and merge target branches match the intended landing branch before creating a mission specification.

Can I use a discovery interview to lock scope before generating a mission specification?

Yes, a structured discovery interview blocks progress until your intent, constraints, and success outcomes are clear, ensuring the mission specification has validated scope before planning begins.

What is the best way to validate requirement quality during spec generation?

The best way to validate requirement quality is applying a checklist-based spec validation that enforces strict requirement formatting and blocks mission creation until all readiness criteria pass.