skills.rest
GarethJB
GarethJBCOMMUNITY
Explore all skills by this author →
GitHub

spec-writing

Create structured 15-section Specs from planning documents or interactive briefs.

Updated Apr 13, 2026
Search Tags:#workflow#planning#documentation#requirements#traceability#spec-writing#sot
One-click install
npx skills add https://github.com/GarethJB/workflow-plugin --skill spec-writing-garethjb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-writing
Source: https://github.com/GarethJB/workflow-plugin/tree/main/skills/spec-writing
Command: npx skills add https://github.com/GarethJB/workflow-plugin --skill spec-writing-garethjb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec writing often becomes inconsistent when planning documents are scattered or informal conversations drift. This skill guides teams to produce precise, structured Specs that serve as the Single Source of Truth (SOT) and contract for development, testing, and validation.

Core Features & Use Cases

  • Maps planning inputs to the 15-spec sections (Definition, Contract, Realization, Assurance) to ensure consistent coverage.
  • Supports both document-based planning and interactive briefs, guiding the user to complete the Spec, with changelog support for traceability.
  • Enforces a draft workflow and provides clear entry points for reviews, edits, and versioning across the pipeline.

Quick Start

Provide a planning document or start an interactive briefing to begin shaping a 15-section Spec.

Frequently Asked Questions about spec-writing

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

FAQPage Schema
How do I create structured software requirements from planning documents?▼

Structured specs serve as the Single Source of Truth (SOT) and contract for development, testing, and validation. They prevent inconsistencies that arise when planning documents are scattered or informal conversations drift away from core requirements.

Can I generate a feature spec through an interactive briefing instead of uploading a document?▼

You can start by providing a planning document or initiating an interactive briefing. The skill then guides you to complete the 15-section Spec, capturing decisions, dependencies, and a changelog for version traceability across the pipeline.

What is the best way to maintain traceability across feature updates and bug fixes?▼

Spec writing applies to new features, updates, and bug fixes. By enforcing a draft workflow with Definition, Contract, Realization, and Assurance groups, it ensures consistent coverage and captures decisions for development and validation.

Does this spec writing workflow work for both new features and bug fixes?▼

The skill requires no specific dependencies and supports both document-based and conversational inputs. You can start immediately by providing a planning document or starting an interactive briefing to shape the spec.

Related Skills

Explore More Software Engineering Skills→
Clos01Clos01
3

pm-spec

Create structured product requirement documents with goals, metrics, and delivery plans.

Community
Intermediate
rhussrhuss
107

implement

Generate implementation plans and TDD cycles from validated specifications.

Community
Basic
DrLuggelsDrLuggels
3

changelog-automation

Generate changelogs and release notes from Conventional Commits.

Community
Advanced
olivermorgan2olivermorgan2

idea-to-prd

Generates a standardized eight-section PRD draft from unstructured notes.

Community
Intermediate