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.