software-design
Software Design
This skill turns a PRD and a published backlog into a clear design: named
modules, located seams, an explicit testing strategy, and TDD-ready issue
bodies that /tdd or /implement can carry one behavior at a time.
It is an orchestration wrapper: the deep-module/seam vocabulary and
testability doctrine live in /codebase-design; the ubiquitous-language
grounding lives in /domain-modeling. This skill calls both and contributes
the glue they lack — the prereq gate, the frontend routing stamp, the
confirmation loop, and the batch tracker mutation.
Backend services and code with real I/O boundaries are the sharpest use
case. UI component trees route to /frontend-design — this skill stamps the
routing block and hands off; it does not design components.