What problem does it solve? Designing a high-level system architecture requires structured decisions about components, boundaries, and data flows, and doing it ad hoc leads to inconsistent or technology-premature documentation. This Skill runs a disciplined, human-in-the-loop interview process to produce a conceptual architecture document that stays free of technology lock-in. ## Core Features & Use Cases - Structured architecture interview: Asks the user clarifying questions with at least three options (each with pros and cons) whenever information is not documented, never guessing on the user's behalf. - Conceptual deliverables: Produces a system context diagram, component/layer breakdown, mermaid data-flow diagrams derived from the real user journey, AI orchestration boundaries, and cross-cutting concerns (audit, RBAC, resilience). - Controlled file writing: Shows the full draft for review before writing, then delegates file creation to an architecture-writer sub agent that updates docs/02-design/02-technical/architecture.md and optionally syncs section 3 of the system design document. - Use Case: A PM or SA asks to draft the Projexa system architecture; the Skill reads the design document and user journey, interviews the user on undocumented decisions, presents diagrams for confirmation, and writes the confirmed architecture document. ## Quick Start Ask the assistant to create or update the high-level conceptual architecture document for the Projexa project.
