architecture-session-playbooklisted

# Architecture Session Playbook **Read [`references/PLAYBOOK.md`](references/PLAYBOOK.md) before applying any of this.** That file is the standard; everything below it is a summary to help you decide whether this skill applies and to check your work afterwards. ## What this standard covers - Why this exists - Session prompt template - What to attach to the session - Choosing REVIEW vs MODERNIZE - Output conventions ## Why this exists [`docs/architecture/00-REFERENCE-ARCHITECTURE.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/architecture/00-REFERENCE-ARCHITECTURE.md) in this repo is the one architectural constitution for the estate: 15 principles, each backed by a working example in copilot-scope or the reference SaaS, plus a compliance checklist. It must not be re-derived from scratch in every session — an agent should read it, not reconstruct it from first principles each time. Two systems already broadly follow it, with known deviations catalogued: - `copilot-scope/docs/architecture/ARCHITECTURE_REVIEW.md` - `<saas>/docs/architecture/ARCHITECTURE_REVIEW.md` The legacy monorepo predates the architecture and is being modernized toward it; its `docs/architecture/` directory (`00-SECURITY-IMMEDIATE.md` … `07-STANDARDS-FEEDBACK.md`) is the worked example of what a RECOVER session produces. --- Generated from [`docs/PLAYBOOK.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/PLAYBOOK.md) by `scripts/build-marketplace