design-gate
Installation
SKILL.md
Design Gate
Pick the design lenses a planned slice actually needs, apply them, and merge their findings into one proceed or revise verdict.
Workflow
- Identify the surfaces that the plan, slice contract, or changed scope touches. Reuse decisions already settled for the feature while their scope, assumptions, and sources still match. Re-route only when evidence changes the design surface.
- Select lenses from the table for each unresolved decision or changed risk. Start with up to three, one per central risk, each with a bounded scope. Add another only for another material risk. When no row matches a local change, return
proceedwith "no design gate required". - Apply each lens read-only in the current role. Dispatch a specialist seat only when a risk needs expertise or independence the current role lacks. Give it the design problem, the files and boundaries in scope, and the gate result shape.
- Merge. A concrete, load-bearing finding from any lens makes the verdict
revise; load-bearing means it changes boundaries, data ownership, contracts, or correctness. Style and speculative findings are advisory. - On
revise, list the required plan changes. After they land, recheck only the lens that raised the blocker. When the lenses expose a real trade-off that only the user's preference can settle, setdecision_requiredand stop.