Guided, section-by-section design document authoring for a specific building system. Gathers context from existing docs, walks through each required section collaboratively, and writes incrementally to file.
A system name argument is required. If missing, fail with usage message. Normalize to kebab-case for filename.
design/architectural/project-brief.md — fail if missingdesign/architectural/systems-index.md — fail if missing.claude/docs/technical-preferences.md for project configurationCreate the design document with empty section headers using the 8 required sections:
# [System Name]
> **Status**: In Design
> **Author**: [user + agents]
> **Last Updated**: [today's date]
## Overview
[To be designed]
## Design Intent
[To be designed]
## Technical Requirements
[To be designed]
## Calculations
[To be designed]
## Code Compliance
[To be designed]
## Coordination Notes
[To be designed]
## Material Specifications
[To be designed]
## Acceptance Criteria
[To be designed]
Walk through each section following:
Context → Questions → Options → Decision → Draft → Approval → Write
Write each section to file immediately after approval.
Update production/session-state/active.md after each section.
/design-review to validate| System Category | Primary Agent | Supporting Agent(s) |
|---|---|---|
| Structural frame, foundations | structural-engineer-lead | foundation-engineer, concrete-specialist |
| HVAC, ventilation | hvac-engineer | energy-modeler, mep-director |
| Electrical, lighting | electrical-engineer | energy-modeler |
| Plumbing, drainage | plumbing-engineer | mep-director |
| Fire protection | fire-protection-engineer | safety-manager |
| Building envelope | facade-engineer | energy-modeler, materials-specialist |
| Interior spaces | interior-design-lead | space-planner, materials-specialist |
| Site/landscape | landscape-architect | geotechnical-engineer |