skills.rest
yoshisada
yoshisadaCOMMUNITY
Explore all skills by this author →
GitHub

specify

Convert natural language feature descriptions into structured spec.md files.

Updated Mar 26, 2026
Search Tags:#automation#workflow#planning#specification#feature#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill specify-yoshisada
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-kiln/skills/specify
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill specify-yoshisada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update feature specifications from natural language descriptions to accelerate planning and ensure alignment between stakeholders and delivery teams.

Core Features & Use Cases

  • Generate complete feature specifications including user stories, functional requirements, and acceptance criteria.
  • Support refinement of existing requirements and branch-based planning within a spec-kit project structure (.specify/ directory).
  • Document assumptions and provide traceability for decisions.

Quick Start

Provide a natural language description of the feature to generate a complete spec.md with user stories, functional requirements, and acceptance criteria.

Frequently Asked Questions about specify

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

FAQPage Schema
How do I convert natural language feature descriptions into structured product specifications?▼

To convert natural language feature descriptions into structured product specifications, provide your text input to generate a complete spec.md containing user stories, functional requirements, and acceptance criteria for stakeholder alignment.

What's the best way to generate user stories and acceptance criteria from a rough feature idea?▼

Generating user stories and acceptance criteria from a rough idea requires submitting the natural language description to produce a structured spec.md, which documents assumptions and provides traceability for delivery team decisions.

Can I refine existing requirements within a spec-kit project structure?▼

You can refine existing requirements within a spec-kit project structure by applying the tool to the .specify/ directory, supporting branch-based planning and updating the spec.md with newly parsed functional requirements.

Does generating feature specifications require a specific directory structure?▼

Generating feature specifications operates within a spec-kit project structure using the .specify/ directory, producing a machine-readable spec.md that supports extension hooks for customization and downstream planning automation.

How do I document assumptions and provide traceability for feature planning decisions?▼

To document assumptions and provide traceability for feature planning decisions, the specification process automatically captures contextual inputs from the natural language description and outputs them within the structured spec.md file.

Related Skills

Explore More Product & Management Skills→
richardnguyen0715richardnguyen0715

speckit-specify

Convert natural language feature descriptions into structured specification documents.

Community
Intermediate
epieczkoepieczko

epic.decompose

Parse Markdown Epic documents and generate structured user stories as JSON.

Community
Intermediate
aimonk2025aimonk2025
3

gtm-strategy

Translate business goals into structured event specifications for GTM tracking plans.

Community
Intermediate
infinith4infinith4
1

requirements

Translate product ideas into structured requirements documentation with traceability matrix.

Community
Advanced