skills.rest
mattphanm
mattphanmCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec

Generate TaskSpec, WorkstreamSpec, or MasterSpec documents from requirements.md.

Updated Mar 23, 2026
Search Tags:#documentation#specification#requirements#spec#approval#task-spec#workstream
One-click install
npx skills add https://github.com/mattphanm/Codex-Agentic --skill spec-mattphanm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/mattphanm/Codex-Agentic/tree/main/.codex/skills/spec
Command: npx skills add https://github.com/mattphanm/Codex-Agentic --skill spec-mattphanm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Specifications are the authoritative contract that prevents scope creep and misinterpretation during implementation, aligning design, development, and testing from a single source of truth.

Core Features & Use Cases

  • Generates TaskSpec, WorkstreamSpec, or MasterSpec documents from gathered requirements.
  • Validates prerequisites (spec group directory, requirements.md, and manifest.json) and records decisions for traceability.
  • Supports a structured spec workflow from /prd to /spec, including requirements extraction, context/goal definition, risk/open questions, and task planning.
  • Useful for coordinating multi-workstream efforts via orchestrated specs with clear interfaces and acceptance criteria.

Quick Start

Follow the workflow by providing a spec group and requirements, then run the /spec command to generate the spec.md.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I generate a specification document from gathered requirements?▼

To generate a specification document, provide a spec group and your requirements, then run the /spec command to produce a spec.md file. This creates an authoritative contract to prevent scope creep during implementation.

What is the best way to coordinate specifications across multiple workstreams?▼

Coordinating multi-workstream efforts requires orchestrated MasterSpec or WorkstreamSpec documents. These specifications establish clear interfaces and acceptance criteria across teams to prevent misinterpretation during development.

What prerequisites do I need to validate before drafting a task specification?▼

Before drafting a task specification, you must validate the existence of a spec group directory, a requirements.md file, and a manifest.json file. These prerequisites ensure structured workflow traceability and proper context.

How does a structured spec workflow prevent scope creep in software development?▼

A structured spec workflow prevents scope creep by enforcing requirements extraction, context definition, risk identification, and task planning. This process creates a single source of truth aligning design, development, and testing.

Can I record decisions and traceability context within my specification workflow?▼

Yes, the specification workflow explicitly records decisions and progress within the generated spec.md file. This structured approach ensures full traceability from initial requirements through final implementation and testing.

Related Skills

Explore More Product & Management Skills→
miyamo2miyamo2

kiro-spec-init

Generate spec.json and requirements.md from a project description using templates.

Community
Intermediate
burningddolburningddol

speckit-implement

Execute Speckit implementation tasks from tasks.md and plan.md with progress tracking.

Community
Advanced
adrianliechtiadrianliechti
4

write-spec

Convert vague feature ideas into structured PRDs with goals and scope.

Community
Advanced
davekim917davekim917
1

team-plan

Convert approved designs into structured task plans with dependencies and acceptance criteria.

Community
Advanced