Architectural Design

Think through system design decisions rigorously before writing them down. This skill is about the thinking — requirements, components, trade-offs, boundaries. When the design is ready, you MUST invoke Skill("write-docs") to write the design document — do not write the doc inline.

Scale to Complexity

Not every decision needs all 5 phases. Match the depth to the decision:

• Small (single component, clear constraints) — Phase 1 briefly, Phase 2, Phase 5. Skip deep dive and scaling.
• Medium (multi-component, some unknowns) — All 5 phases, but keep each concise.
• Large (new system, significant unknowns, cross-team) — All 5 phases in full depth, with diagrams and explicit load estimates.

Red Flag