spec-authoring

Generate structured software specifications with requirements, user stories, and acceptance criteria.

1|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/datamaker-kr/synapse-claude-marketplace --skill spec-authoring-datamaker-kr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-authoring
Source: https://github.com/datamaker-kr/synapse-claude-marketplace/tree/main/plugins/speckit-helper/skills/spec-authoring
Command: npx skills add https://github.com/datamaker-kr/synapse-claude-marketplace --skill spec-authoring-datamaker-kr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that software requirements are clearly defined, unambiguous, and easily testable, preventing costly misunderstandings and rework during development.

Core Features & Use Cases

  • Structured Specification Generation: Creates documents with defined sections for overview, requirements, data models, and API contracts.
  • Requirement Numbering & Traceability: Enforces consistent IDs (FR-XXX, NFR-XXX) for easy tracking.
  • User Story Decomposition: Breaks down features into actionable user stories with acceptance criteria.
  • Quality Validation: Applies a checklist to ensure completeness and clarity before finalization.
  • Use Case: When a product manager needs to define a new feature, this Skill can help draft a spec.md file that includes user stories, functional requirements, and acceptance criteria in the correct format.

Quick Start

Use the spec-authoring skill to draft a new specification document for the 'user authentication' feature.

Frequently Asked Questions about spec-authoring

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

FAQPage Schema
How do I write testable software specifications with clear acceptance criteria?

Software specification documents should include defined sections for overview, requirements, data models, and API contracts. Enforcing standardized templates and quality checklists ensures completeness and facilitates clear communication between product, design, and engineering teams.

What is the best way to structure a spec.md file for product features?

A structured spec.md file should include an overview, functional requirements, data models, API contracts, and user stories with acceptance criteria. Using consistent requirement IDs like FR-XXX ensures traceability and clear communication across product and engineering teams.

How do I break down product requirements into actionable user stories?

Breaking down product requirements involves decomposing features into actionable user stories paired with specific acceptance criteria. Applying a quality validation checklist ensures these stories are complete, unambiguous, and easily testable before development begins.

Does requirement traceability require unique IDs for functional and non-functional requirements?

Requirement traceability requires consistent unique IDs, specifically using formats like FR-XXX for functional requirements and NFR-XXX for non-functional requirements. This numbering system allows product and engineering teams to easily track specifications throughout development.

Can I generate API contracts and data models within a software specification document?

Generating API contracts and data models is supported directly within the software specification document. The specification includes dedicated sections for these components to ensure engineering teams receive structured, unambiguous technical definitions alongside user stories.