specs-to-business

Generate human-readable business documentation from OpenSpec master specifications.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/kxnzee/multi-repo-specs --skill specs-to-business-kxnzee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specs-to-business
Source: https://github.com/kxnzee/multi-repo-specs/tree/main/extensions/spec-reader/skills/specs-to-business
Command: npx skills add https://github.com/kxnzee/multi-repo-specs --skill specs-to-business-kxnzee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical specifications written in OpenSpec format with GIVEN/WHEN/THEN scenarios are hard for business stakeholders to read. This Skill converts master specs into plain-language Markdown documentation without losing any requirements, scenarios, or normative details. ## Core Features & Use Cases - Lossless Paraphrasing: Converts every Requirement and Scenario into plain business language while preserving actors, preconditions, exceptions, negations, numbers, and requirement strength (MUST/SHOULD/MAY). - Full Traceability: Each generated document includes a source-mapping appendix linking every requirement and scenario back to its exact line in the original spec.md, plus Git HEAD and SHA-256 provenance metadata. - Scoped Generation: Processes a single named capability by default, or the entire system only on explicit request, writing results to docs/business/ with collision and symlink safety checks. - Use Case: A product manager needs to present the authentication requirements to stakeholders. Run the Skill on the authentication capability to produce docs/business/authentication.md with plain-language descriptions and a complete source-traceability table. ## Quick Start Ask the agent to create business documentation from the master spec for the authentication capability in the current OpenSpec store.

Frequently Asked Questions about specs-to-business

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

FAQPage Schema
How do I generate business documentation from OpenSpec specifications?▼

Name the capability you want documented and the Skill reads its spec.md from openspec/specs/, then writes a plain-language Markdown file to docs/business/. Full-system documentation is generated only when you explicitly request all master specs.

What is the difference between master specs and changes in OpenSpec?▼

Master specs in openspec/specs/ describe the current accepted requirements and are the only source this Skill reads. Changes, proposals, tasks, and archived deltas are explicitly excluded and never treated as additional requirements.

Does the generated documentation confirm the feature is implemented?▼

No. Every document is marked as a derived representation of the master spec, not confirmation of implementation. The Skill describes what the specification prescribes, never what the product actually does.

Can I update existing business docs without losing manual edits?▼

Yes. The Skill only updates files carrying its generator comment. Files without the marker or containing marked manual additions are preserved, and the Skill asks how to proceed instead of overwriting them.

What happens when the source specification contains contradictions or TBD items?▼

Contradictions and unresolved TBD items are never silently fixed. They are listed in a dedicated unclarities section of the output document with links back to the exact source locations for human review.