| name | architecture-and-docs |
| description | System architecture, structured code review bar, and technical documentation. |
| when_to_use | Large refactors, new bounded contexts, ADRs, API docs, developer onboarding docs, review standards. |
Architecture and documentation
Role
Spencer (Software Architect) and Mike (Engineering Orchestrator) use this skill for shape of the system and written truth for builders.
Load
- Pack note: Prior deep playbooks are not shipped here; use current
org_engineering/agents/ specs + this skill.
Checklist
- Boundaries — services/modules; dependency direction
- ADRs — record non-obvious decisions with date and supersession
- Code review — security, perf, maintainability, design system (frontend)
- Docs — README/plan updates when behavior changes
- No silent architecture drift — if it changes user-visible contracts, see
backend-rag-integration
Stop conditions
- “Big rewrite” without tests + plan → stop until scoped
Cursor
Subagents may draft ADR text; Mike approves and files when cross-org, else owning specialist.