skills.rest
joestump
joestumpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec

Create and maintain paired OpenSpec specification and design documents.

30|2|Updated Feb 13, 2026
Search Tags:#architecture#mermaid#requirements#adr#spec#openspec#rfc2119
One-click install
npx skills add https://github.com/joestump/claude-plugin-design --skill spec-joestump
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/joestump/claude-plugin-design/tree/main/skills/spec
Command: npx skills add https://github.com/joestump/claude-plugin-design --skill spec-joestump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The spec skill removes ambiguity and drift between requirements and architecture by producing and maintaining paired specification and design documents so teams have a single, synchronized source of truth for a capability.

Core Features & Use Cases

  • Paired artifact creation: always create or update both spec.md (requirements) and design.md (architecture and rationale) together.
  • Governance and validation: enforces RFC 2119 normative language, SPEC-XXXX sequential numbering, required scenario formatting, and Mermaid diagrams in design.md.
  • Team workflows: supports single-agent drafting or multi-agent team review via TeamCreate to produce review-ready artifacts and summarize outcomes.
  • Use cases: drafting new capabilities, converting ADRs into formal specs, updating existing specs, and integrating spec locations into project CLAUDE.md.

Quick Start

Create a new SPEC for a payment-webhook capability and produce both spec.md and design.md under docs/openspec/specs/payment-webhook.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I create paired spec and design documents for a new software capability?▼

To create paired spec and design documents, use the spec skill to generate synchronized spec.md for requirements and design.md for architecture under docs/openspec/specs/, enforcing RFC 2119 normative language and Mermaid diagrams automatically.

How do I convert an ADR into a formal OpenSpec specification?▼

Converting an ADR into a formal OpenSpec specification involves transforming architectural decisions into the SPEC-XXXX format, generating paired spec.md and design.md files with required scenario formatting and sequential numbering.

What is the best way to enforce RFC 2119 normative language in software requirements?▼

Enforcing RFC 2119 normative language in software requirements is achieved by applying the spec skill to draft or update documents, ensuring consistent use of MUST, SHOULD, and SHALL across synchronized specification and design artifacts.

Can I use Mermaid diagrams in design documents for architecture rationale?▼

Yes, you can use Mermaid diagrams in design documents to visualize architecture and rationale. The spec skill enforces the inclusion of Mermaid diagrams within the design.md file for every generated software capability specification.

Does the spec workflow support multi-agent team review for specifications?▼

Yes, the spec workflow supports multi-agent team review via TeamCreate orchestration, allowing multiple agents to validate and review the paired specification and design documents before producing final review-ready artifacts and outcome summaries.

How do I maintain synchronized requirements and architecture documents without drift?▼

Maintaining synchronized requirements and architecture documents without drift requires enforcing paired updates to both spec.md and design.md simultaneously, ensuring teams always have a single source of truth for any software capability.

Related Skills

Explore More Software Engineering Skills→
Alan-TheGentlemanAlan-TheGentleman
10

sdd-design

Translate proposals and specs into architecture decisions and data flow in design.md.

Community
Advanced
pameliapamelia

spec-review

Orchestrate a three-phase multi-agent spec review with self-critique and cross-review.

Community
Advanced
TraftGTraftG
33

architecture-decision

Generate ADR-XXXX files with Context, Decision, Consequences, and Alternatives sections.

Community
Advanced
kayamankayaman
1

rfc2119

Enforce RFC 2119 keyword capitalization and usage in technical documents.

Community
Intermediate