speckit-specify

Generate a feature specification from a natural language description within a spec-kit project.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/gkuga/monit-rs --skill speckit-specify-gkuga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/gkuga/monit-rs/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/gkuga/monit-rs --skill speckit-specify-gkuga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, testable specification is slow and inconsistent. This Skill converts a plain-language feature description into a complete spec.md file with user scenarios, functional requirements, and measurable success criteria, following the spec-kit workflow. ## Core Features & Use Cases - Automated Branch and Spec Setup: Generates a short branch name, runs the create-new-feature script, and initializes the spec file from the project template. - Structured Specification Generation: Produces user scenarios, functional requirements, success criteria, and key entities while limiting open questions to three [NEEDS CLARIFICATION] markers. - Quality Validation Loop: Creates a requirements checklist, validates the spec against it, and iterates up to three times to resolve issues before reporting readiness. - Use Case: A product manager types a feature idea like "add OAuth2 login for the mobile app" and receives a ready-to-plan specification on a new feature branch, complete with a quality checklist. ## Quick Start Ask the assistant to create a feature specification by describing the feature you want, for example: specify a user authentication feature with OAuth2 support.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I create a feature specification from a text description?

Provide a natural language description of the feature as the command argument. The Skill generates a branch name, creates the feature branch via the create-new-feature script, and writes a complete spec.md with scenarios, requirements, and success criteria.

What is spec-kit and how does the specify command fit in?

Spec-kit is a spec-driven development workflow where features start as written specifications. The specify step is the first phase, producing spec.md, which later feeds into the clarify and plan phases.

Does speckit-specify require a specific project structure?

Yes, it requires a spec-kit project with a .specify directory containing scripts and templates, including create-new-feature.sh and spec-template.md. Without this structure the branch creation and spec initialization steps cannot run.

How many clarification questions can a specification contain?

A maximum of three [NEEDS CLARIFICATION] markers are allowed per specification. The Skill prioritizes them by impact: scope first, then security and privacy, then user experience, and makes informed guesses for everything else.

Why does spec validation fail after generation?

Validation fails when the spec contains implementation details, untestable requirements, non-measurable success criteria, or unresolved clarification markers. The Skill updates the spec and re-validates up to three iterations before reporting remaining issues.