What problem does it solve? Teams often jump from business requirements straight to technology choices without writing down the technical constraints those requirements force, leaving architectural decisions unjustified. This Skill translates each reviewed business requirement into implementation-neutral technical requirements with full traceability, before any technology decisions are made. ## Core Features & Use Cases - BR-to-TR translation: Walks the reviewed business-requirements.md and derives numbered TR-NN entries, each citing its source BR-NN plus optional capability, UX, or prior ADR context via Hugo ref links. - Append-only living document: Preserves existing TR numbering on re-extraction, flags stale source links with warning markers instead of deleting them, and resets the reviewed_at gate when contents change. - Decision separation: Refuses to record technology choices as requirements, parking volunteered solutions in Open Questions for the downstream plan-adrs and define-adr stages. - Use Case: After reviewing business-requirements.md for a self-hosted application platform capability, run this Skill to produce tech-requirements.md with TRs like tenant data export and isolation constraints, each traceable to its BR, ready for human review before ADR planning begins. ## Quick Start Extract the technical requirements for the self-hosted-application-platform capability from its reviewed business-requirements.md.
