What problem does it solve?
This Skill prevents costly architectural violations and rework by enforcing architectural constraints at the earliest stage: requirements definition. It ensures that all new feature requirements are explicitly aligned with the project's core architecture principles from the start, avoiding design flaws that lead to significant refactoring later.
Core Features & Use Cases
- Mandatory Document Reading: Before any requirements analysis, it forces the user to read and confirm understanding of core architectural and business rules documents, ensuring foundational knowledge.
- Architecture Constraint Enforcement: Ensures every requirements document includes a dedicated "Architecture Constraints" section, detailing technical boundaries, aggregation root principles, and technical blacklists.
- Violation Termination: Automatically terminates tasks if architectural rules are violated during requirements generation (e.g., missing architecture constraint sections), preventing flawed requirements from progressing.
- Use Case: A user requests a new feature. This Skill first ensures they've read the core architecture documents. Then, it automatically generates a requirements document template that includes a mandatory "Architecture Constraints" section, pre-filled with relevant rules like "Write operations must go through MedicalCase aggregate root," guiding the user from the outset.
Quick Start
Create a new requirements document for "Enhanced patient search," ensuring architectural constraints are included.
