rules - Technical Design and Constraints: Capture Feature-Level Rules
Translate spec and acceptance criteria into feature-level design decisions and validatable technical constraints written to spec/rules.md.
Tags
Updated: 2026-06-30Capabilities
Typical Inputs
Typical Outputs
What this skill does
- Read spec and acceptance criteria files
- Read project convention and build files
- Survey ecosystem frameworks and libraries
- Ask user for design decision resolution
- Write technical design rules with IDs
- Map acceptance criteria to rules
- Route product ambiguities back to spec
Inputs
- Resolved spec file (spec/spec.md)
- Acceptance criteria file (spec/criteria.md)
- Proposal file (spec/proposal.md)
- Project convention files (CLAUDE.md, AGENTS.md, GEMINI.md)
- Build files (Gradle, Maven, package.json)
- Existing source layout, ADRs, docs/architecture
Outputs
- spec/rules.md with design overview, rules, and cross-reference table
- Design decisions recorded as validatable constraints
- Acceptance criteria to rules cross-reference table
Requirements
- AskUserTool available for interactive resolution
- Read access to project files and source layout
- Spec and criteria files must exist and be resolved