designlisted

Use when the shape of a system is being decided or reviewed: a purpose brief, a process map, an architecture decision record, a technology map, a conceptual to logical to physical data model, diagrams as code, or a verification plan. Runs the six design phases in order, each gating the next, and checks the dossier for the artifacts its tier requires. Invoke as /brothersbe:design.
khalilmaaouni/BrotherSBE · ★ 0 · Web & Frontend · score 68

Install: claude install-skill khalilmaaouni/BrotherSBE

# Design Design comes before verification. The expensive mistakes are made while deciding what to build, how the process runs, what shape the system takes, and how the data is modeled. Checking the result at the end catches none of them. ## Load the law for the phase you are in, and not the rest Read `${CLAUDE_PLUGIN_ROOT}/SKILL.md` first, then load only what the routing table sends you to: | You are doing this | Read | |---|---| | purpose brief, process map | `${CLAUDE_PLUGIN_ROOT}/references/phases-purpose-and-process.md` | | architecture, technology map, data model | `${CLAUDE_PLUGIN_ROOT}/references/phases-architecture-and-data.md` | | diagrams, dossier documentation | `${CLAUDE_PLUGIN_ROOT}/references/phase-expression.md` | | tiering a task, checking required artifacts | `${CLAUDE_PLUGIN_ROOT}/references/laws-tier-and-artifacts.md` | | writing or reviewing an ADR, data model or diagram | `${CLAUDE_PLUGIN_ROOT}/references/laws-design-artifacts.md` | | consulting a decision table | `${CLAUDE_PLUGIN_ROOT}/references/laws-decision-tables.md` | ## The artifacts Templates live in `${CLAUDE_PLUGIN_ROOT}/templates/dossier/`, numbered in the order they are written: 01 purpose, 02 process, 03 ADR, 04 technology map, 05 data model, 06 diagrams, 07 verification. The tier decides which are required. An architecture decision is taken from a decision table with named criteria and thresholds (`${CLAUDE_PLUGIN_ROOT}/tables/`), and the ADR records the recommendation, the first and s