What problem does it solve? Capability and user experience docs describe business intent but are not testable or auditable on their own. This Skill extracts a numbered, source-linked list of business requirements (BR-01, BR-02, ...) from those docs, creating the reviewable contract that technical requirements and ADRs must trace back to. ## Core Features & Use Cases - Sourced requirement extraction: Reads the capability doc and every UX doc under docs/content/capabilities/{name}/, then derives business requirements with Hugo ref shortcode links back to their exact source sections. - BR/TR/decision boundary enforcement: Refuses to accept technical requirements (cadences, thresholds) or decisions (technologies, protocols) as BRs, parking them in Open Questions for the TR or ADR stage instead. - Append-only living document: Preserves BR numbering across re-extractions, flags stale source links with a warning marker instead of deleting them, and gates downstream work on a human-set reviewed_at frontmatter field. - Use Case: After defining a self-hosted application platform capability and its user experiences, run this Skill to produce business-requirements.md with 5+ sourced BRs, review it, set reviewed_at, and only then proceed to technical requirements. ## Quick Start Extract the business requirements for the self-hosted-application-platform capability from its capability doc and user experiences under docs/content/capabilities/.
