speckit-specify

Transform natural-language feature descriptions into structured specification drafts.

1|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/code-dot-org/marketing-sites --skill speckit-specify-code-dot-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/code-dot-org/marketing-sites/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/code-dot-org/marketing-sites --skill speckit-specify-code-dot-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update the feature specification from a natural language feature description.

Core Features & Use Cases

  • Generate a complete feature spec including user scenarios, functional requirements, non-functional requirements, success criteria, and risks.
  • Allow for iterative refinement with prompted clarifications, assumptions, and validation steps.
  • Provide a ready-to-share spec aligned to an execution template for planning and review.

Quick Start

Describe your feature in plain language to generate a complete specification draft.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I turn a natural language feature description into a structured specification?

To turn a natural language feature description into a structured specification, input your plain text concept and the system generates a plan-ready draft including user scenarios, functional requirements, and success criteria.

What should a complete feature specification include for project planning?

A complete feature specification should include user scenarios, functional and non-functional requirements, success criteria, risks, and validation steps to ensure comprehensive project planning and review.

Can I refine requirements and add clarifications to an existing specification draft?

You can iteratively refine requirements through prompted clarifications and assumptions, allowing you to validate steps and update the specification draft continuously until it meets your planning needs.

How do I validate assumptions when writing requirements for a new feature?

To validate assumptions when writing requirements, the system prompts you for specific clarifications during the specification generation process, ensuring all functional requirements and user scenarios are fully testable.

Does this specification tool provide a standardized template for feature planning?

The specification tool provides a ready-to-share output aligned to a standardized execution template, ensuring your feature ideas are transformed into plan-ready specifications for immediate review.