Step 3: Design artifacts, optional
Purpose
Section titled “Purpose”Create architecture diagrams and decision records that explain the approved design. Keep the diagram source with its rendered output.
Step 3 is optional. If the design is already documented, proceed to Step 3.5 Governance.
04-Design
uses the
apex-python-diagrams
and
apex-azure-adr
skills.
Invocation
Section titled “Invocation”Select: 04-Design in Copilot ChatOutput: agent-output/{project}/03-des-diagram.py + .png + .svg agent-output/{project}/03-des-adr-*.mdArtifact types
Section titled “Artifact types”| Artifact | Tooling | Purpose |
|---|---|---|
| Architecture diagram | apex-python-diagrams | Reproducible Azure system view |
| Runtime-flow diagram | apex-python-diagrams | Request paths and async messaging |
| Dependency diagram | apex-python-diagrams | Resource dependency tree |
| ADR | apex-azure-adr skill | WAF-mapped decisions with alternatives |
Review
Section titled “Review”Review is opt-in. When requested, use a comprehensive review of the design
decision records through the 10-Challenger handoff.
Hand-off
Section titled “Hand-off”Select Step 3.5: Governance when the design artifacts are ready.