What is the primary purpose of the OpenSpec Authoring skill?

It enforces specific formatting and structural conventions for technical documentation, including proposals, task lists, and system specifications, ensuring consistency across a project.

Which files does this skill typically manage?

It is designed to work with proposal.md, tasks.md, and spec.md files within an OpenSpec-compliant project directory structure.

How does it handle change tracking?

It utilizes standardized metadata blocks and verb-led, kebab-case Change IDs (e.g., add-feature-x) to track the status, date, and authorship of every document update.

Can it validate my documentation structure?

The skill includes a validation checklist to ensure all referenced capabilities exist, paths use workspace-relative notation, and specific section orders are maintained.

Does this skill support BDD-style requirements?

Yes, it specifically enforces Given/When/Then patterns for requirement scenarios to ensure they are testable, behavior-focused, and clear for implementation.

OpenSpec Authoring

Name: OpenSpec Authoring
Author: ricardoroche

byricardoroche

Learning & Documentation

Enforces standardized OpenSpec conventions for technical proposals, task tracking, and requirement specifications.

About

The OpenSpec Authoring skill empowers Claude to act as a precision-focused technical writer by enforcing strict organizational patterns for project documentation. It ensures that proposals, task lists, and specifications follow a uniform structure—including metadata blocks, verb-led change IDs, and BDD-style Given/When/Then scenarios. This skill is ideal for teams following the OpenSpec methodology who need to maintain consistency across project deltas, architectural decisions, and validation checklists while ensuring all documentation remains testable and behavior-focused.

Key Features

Archiving workflows for post-deployment documentation management
Strict metadata block enforcement for tracking status and authorship
Standardized proposal structure from executive summary to risk mitigation
0 GitHub stars
BDD-style requirement patterns using Given/When/Then scenarios
Automated task grouping with built-in validation checklists

Use Cases

Drafting new technical proposals with consistent executive summaries and scoping
Creating testable requirements with associated behavioral scenarios for developers
Managing project tasks and spec deltas during complex feature implementations

About

Key Features

Archiving workflows for post-deployment documentation management
Strict metadata block enforcement for tracking status and authorship
Standardized proposal structure from executive summary to risk mitigation
0 GitHub stars
BDD-style requirement patterns using Given/When/Then scenarios
Automated task grouping with built-in validation checklists

Use Cases

Drafting new technical proposals with consistent executive summaries and scoping
Creating testable requirements with associated behavioral scenarios for developers
Managing project tasks and spec deltas during complex feature implementations