Software EngineeringOpen accessPublished 3 Oct 2026
Expand a rough markdown spec into a high-level architecture & design spec
written for humans — decision-focused prose plus diagrams (SVG), closing with
a build plan / task DAG so the execution shape can be reviewed before
implementation — for design review and cross-team alignment. Use when the
user wants the big-picture architecture, the key decisions, and what each
team must do, NOT an implementation-ready spec.
Contrast with /expand-spec-technical: that skill produces a detailed technical spec
(concrete types, file-level integration points) consumable by both human
implementers and coding agents. This skill stays at the architecture level
and is written predominantly …