skills.rest
syeda-hoorain-ali
syeda-hoorain-aliCOMMUNITY
Explore all skills by this author →
Website𝕏@syedahorainaliGitHub

specification-writing-skill

Define structured feature specifications with YAML frontmatter and spec.md bodies.

Updated Dec 7, 2025
Search Tags:#specification#product-management#user-stories#acceptance-criteria#spec-writing#phase-01#phase-02
One-click install
npx skills add https://github.com/syeda-hoorain-ali/todo-spec-driven-hackathon --skill specification-writing-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specification-writing-skill
Source: https://github.com/syeda-hoorain-ali/todo-spec-driven-hackathon/tree/main/.claude/skills/spec-writing
Command: npx skills add https://github.com/syeda-hoorain-ali/todo-spec-driven-hackathon --skill specification-writing-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Specification Writing Skill helps teams produce clear, testable feature specifications for Spec-Driven Development, reducing ambiguity and rework.

Core Features & Use Cases

  • Template-driven spec creation for Phase-based features
  • Structured requirements mapping (FRs, user scenarios, acceptance criteria)
  • Real-world guidance and checklists for collaborative spec crafting

Quick Start

Ask me to generate a complete feature specification for Phase 01 Todo app with priorities and acceptance criteria.

Frequently Asked Questions about specification-writing-skill

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

FAQPage Schema
How do I write feature specifications that eliminate ambiguity in requirements?▼

Feature specifications eliminate ambiguity by applying a structured format with YAML frontmatter, mapping functional requirements, user scenarios, and acceptance criteria to ensure clear, testable project outcomes.

What is the best way to structure user stories and acceptance criteria for software projects?▼

The best way to structure user stories and acceptance criteria is using a template-driven spec.md body that defines key entities, user scenarios, and success criteria alongside an accompanying Prompt History Records structure.

Can I use this specification writing approach for phase-based feature development?▼

Yes, this specification writing approach supports phase-based feature development by generating template-driven specifications tailored for distinct project phases, such as Phase 01 or Phase 02 features, across various feature types.

How do you generate functional requirements and risk considerations for a feature spec?▼

You generate functional requirements and risk considerations by applying real-world guidance and checklists during collaborative spec crafting, ensuring all practical scenarios and success criteria are documented within the specification.

Does spec-driven development work with YAML frontmatter metadata formats?▼

Spec-driven development conforms to YAML frontmatter metadata formats to define structured feature specifications, ensuring requirements mapping remains clear, testable, and properly organized for software project teams.

Related Skills

Explore More Product & Management Skills→
evanfang0054evanfang0054

brainstorming

Transform user ideas into detailed project designs with scope and architecture.

Community
Intermediate
forztfforztf
9

speckit-analyze-zh

Parse spec.md, plan.md, and tasks.md to generate a structured consistency and quality report.

Community
Advanced
nimeshgurungnimeshgurung

agile-product-owner

Generate INVEST-compliant user stories, acceptance criteria, and sprint plans.

Community
Intermediate
diegosanchespereira1diegosanchespereira1

bmad-create-epics-and-stories

Breaks down planning documents into epics and user stories for delivery planning.

Community
Advanced