What problem does it solve? Implicit technical, regulatory, integration, and operational boundaries often go undocumented until they block implementation. This Skill analyzes a PRD or specification to make those constraints explicit, with rationale, affected requirement IDs, interactions, and risk flags, before technical design or ticket breakdown begins. ## Core Features & Use Cases - Four-Category Constraint Analysis: Surfaces Technical (TC), Compliance (CC), Integration (IC), and Operational (OC) constraints, each with rationale and impact on specific requirement IDs. - Interaction and Risk Mapping: Documents pairwise constraint interactions (reinforcing, conflicting, conditional) and flags high-risk constraints with severity and recommendations. - Append-Only Living Artifacts: Writes analyses to .gener8v/constraints/ with stable IDs, approval status tracking, and in-place amendment so downstream designs and tickets keep valid references. - Use Case: Before designing a search feature, run the Skill on the search specification to discover that the legacy help center has no API (IC-002) and that PII in documentation requires access controls (CC-001), so these boundaries shape the architecture from day one. ## Quick Start Run the constraints skill on the search-and-retrieval specification to surface all technical, compliance, integration, and operational constraints before technical design.
