skills.rest
leonardomoraisf
leonardomoraisfCOMMUNITY
Explore all skills by this author →
GitHub

speckit-specify

Convert natural language feature descriptions into user stories, requirements, and acceptance criteria.

Updated Aug 23, 2026
Search Tags:#workflow#planning#specification#requirements#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-specify-leonardomoraisf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/leonardomoraisf/commonplace-pinboard-extension/tree/main/.agents/skills/speckit-specify
Command: npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-specify-leonardomoraisf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit Specify converts natural language feature ideas into precise, formal specifications to reduce ambiguity and rework during planning.

Core Features & Use Cases

  • Specification generation: outputs user stories, functional requirements, and acceptance criteria from a description.
  • Spec maintenance: creates or updates spec.md in the project using a consistent template.
  • Guided workflow: follows a spec-driven development methodology with outline, checks, and validation steps.
  • Scope guidance: assists starting new features or refining existing requirements for clearer scope.

Quick Start

Provide a natural language feature description after /speckit.specify to generate a complete Spec.md with user stories, functional requirements, and acceptance criteria.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I turn natural language feature descriptions into formal specifications?▼

To turn natural language feature descriptions into formal specifications, provide your text input to generate user stories, functional requirements, acceptance criteria, and a quality checklist for plan-ready outputs.

What is the best way to write user stories and acceptance criteria from a rough feature idea?▼

Writing user stories and acceptance criteria from a rough feature idea involves transforming the text into a spec.md file using a guided, spec-driven development workflow with validation steps.

Can I use this to refine existing requirements for clearer scope alignment?▼

Yes, you can refine existing requirements for clearer scope alignment by processing your current descriptions to output structured functional requirements and validate stakeholder expectations.

Does this approach maintain a consistent specification template across a project?▼

Yes, this specification approach maintains a consistent template by creating or updating a spec.md file in the project, ensuring all feature requirements follow a standardized format.

Why should I use a spec-driven development methodology for planning new features?▼

You should use a spec-driven development methodology for planning new features to reduce ambiguity and rework by generating formal, plan-ready specifications with validation checks before implementation.

Related Skills

Explore More Product & Management Skills→
Rubiss-ProjectsRubiss-Projects
25

speckit-specify

Generate feature specifications from natural language descriptions.

Official
Advanced
JohnnnmaiJohnnnmai
1

user-story

Generate user stories with Mike Cohn format and Gherkin acceptance criteria.

Community
Intermediate
danilonovaisvdanilonovaisv
1

github-project-management

Coordinate GitHub issues, boards, and sprint planning across repositories.

Community
Advanced
shaitamam-80shaitamam-80

product-manager

Translate ideas into structured product specifications with PRD templates and user stories.

Community
Advanced