arch-orchestratorlisted

# Architecture Orchestrator ## Overview Turn a raw product brief into a consistent, implementation-ready spec pack under `specs/` by coordinating specialist agents **and** enforcing a project's preferred stack (frontend, backend, and AI). ## When to Use - User provides a software brief and wants full project architecture/spec docs - User wants "screen-by-screen + backend + API + AI" markdown files - User says "create architecture", "generate specs", "turn my brief into documentation" - User wants an **opinionated** stack (design system + deployment platform) applied consistently across the whole spec pack ## When NOT to Use - Simple one-off questions about architecture patterns - When user already has spec files and just needs edits - Code implementation tasks (use after specs are approved) --- ## Preference System (SOURCE OF TRUTH) ### 1) Preference File Search Order 1. `specs/preferences.yaml` (recommended) 2. `specs/preferences.json` 3. `.arch-orchestrator/preferences.yaml` 4. `.arch-orchestrator/preferences.json` If none exist, **create** `specs/preferences.yaml` using the default template (see `templates/preferences.example.yaml`), and record this in `specs/decisions.md`. ### 2) Design System Sources Search Order 1. `design-system/` folder (any of: `README.md`, `tokens.*`, `components.*`, `patterns.*`, `a11y.*`) 2. `specs/design-system-source.md` 3. `docs/design-system.md` If none exist, generate `specs/design-system.md` as a "Design system not provided" do