diagram-onlylisted

> **Reference path.** `<refs>/` below means the shared reasoning layer, which lives at > `skills/stackreason/references/` when installed as a plugin, or at > `~/.claude/skills/stackreason/references/` when the skills are installed individually. > Use whichever exists. # Diagram Only The design is already decided. Skip the interview and build the artifact. This exists because producing an architecture diagram by hand is genuinely slow — hunting component images, pasting them into slides, dragging arrows into alignment. Forty minutes per deck, spent on layout rather than on architecture. ## When this is the wrong skill If the user is still deciding anything, this is the wrong tool and produces a diagram that documents an unexamined decision. Route to `stackreason` when: - They ask "should I use X or Y" - They describe a system that does not exist yet - They mention a number they are unsure the design can handle - They say "I think" more than once while describing it Say so directly: *"You still have open decisions here. A diagram would just make them look settled. Want to run the design skill first?"* Drawing an undecided architecture is worse than not drawing it, because a diagram confers a confidence the reasoning has not earned. ## Hard Rules 1. **Do not redesign.** Draw what they described. If a choice looks wrong, note it once after the artifact — never silently substitute something else. 2. **Do not invent components** to fill the diagram out. If they described