skills.rest
gmliao
gmliaoCOMMUNITY
Explore all skills by this author →
GitHub

specify

Create structured feature specs with user stories and acceptance criteria.

1|Updated Nov 22, 2025
Search Tags:#specification#requirements#user-stories#acceptance-criteria#feature-definition#project-constitution
One-click install
npx skills add https://github.com/gmliao/swift-state-tree --skill specify-gmliao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/gmliao/swift-state-tree/tree/main/.agent/skills/SpecKit/specify
Command: npx skills add https://github.com/gmliao/swift-state-tree --skill specify-gmliao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to distill requirements into clear, testable specifications, leading to scope creep and ambiguous deliverables. This skill helps capture WHAT is being built and WHY it matters, separating business intent from technical implementation.

Core Features & Use Cases

  • Structured specification creation: Guides the creation of a feature spec with sections like Feature Overview, User Stories, Functional & Non-Functional Requirements, and Acceptance Criteria.
  • Stakeholder alignment: Facilitates consensus by documenting goals, constraints, and success criteria early in the project.
  • Use Case Scenarios: Provides templates and prompts to convert user needs into testable stories and measurable outcomes.
  • Versioned artifact planning: Prescribes a specs/<feature-id>/spec.md structure and branching workflow to manage changes over time.

Quick Start

Start by defining the project constitution and user needs, then draft a spec at specs/001-<feature-id>/spec.md following the template described in this skill.

Frequently Asked Questions about specify

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

FAQPage Schema
How do I write feature specifications that separate business intent from technical implementation?▼

Feature specifications should define WHAT to build and WHY it matters by capturing user stories, functional requirements, and acceptance criteria without detailing HOW to implement it. This prevents scope creep and ambiguous deliverables.

What is the best way to structure user stories and acceptance criteria for a new feature?▼

Structure user stories and acceptance criteria within a versioned feature specification using a dedicated directory like specs/<feature-id>/spec.md. Include sections for Feature Overview, User Stories, Functional & Non-Functional Requirements, and Acceptance Criteria.

How do I stop scope creep when defining project requirements and feature definitions?▼

Stop scope creep by creating a project constitution that documents goals, constraints, and success criteria early. Defining clear feature definitions and testable specifications aligns stakeholders and separates business intent from technical implementation.

Can I use this specification structure to manage changes and versioning over time?▼

Yes, the specification structure manages changes over time by prescribing a versioned artifact planning workflow. It uses a branching workflow alongside the specs/<feature-id>/spec.md structure to track updates to feature definitions.

What should be included in a project constitution to ensure stakeholder alignment?▼

A project constitution ensures stakeholder alignment by documenting project goals, constraints, and measurable success criteria. It captures the core user needs and the WHY behind a feature before drafting the full specification.

Related Skills

Explore More Product & Management Skills→
cuiosscuioss
1

cui-requirements

Generate structured requirements documents and technical specifications.

Community
Basic
J03Fr0stJ03Fr0st

to-tickets

Convert project plans and specifications into structured issue tracker tickets.

Community
Intermediate
julcasansjulcasans

sdd-archive

Merge delta specifications into main project specs and archive completed changes.

Community
Intermediate
dundasdundas

user-story-generator

Generate user stories with acceptance criteria in Markdown format.

Community
Intermediate