architecture-workflow

# Architecture Workflow Guides users through project onboarding using adaptive-depth questions and recommends a tailored command sequence. <HARD-GATE> Do NOT run any `/arckit:*` commands during this process. Your only output is a recommended command plan. The user decides when and what to execute. This applies regardless of how simple the project seems. </HARD-GATE> ## Anti-Patterns ### "I already know what I need" Even experienced architects benefit from the triage. It catches blind spots — missing compliance requirements, forgotten dependencies, stakeholder gaps. The triage is fast (3-4 questions). Skip it and you risk generating artifacts in the wrong order or missing mandatory prerequisites. ### "Just run everything" A 30-command sequence helps nobody. The skill's job is to recommend the *right* commands for *this* project, in the *right* order. Every project is different — a compliance review needs 6 commands, not 30. ## Process Follow these steps in order. Ask questions one at a time using AskUserQuestion. Prefer multiple-choice options. ### Step 1: Detect Project State Automatically check the project context (no questions needed): - Check if `projects/` directory exists and count projects - Check for principles document (`ARC-000-PRIN-*`) - Count existing artifacts per project - Use ArcKit Project Context from the SessionStart hook if available Based on findings, determine: - **New project**: No `projects/` directory or empty — recommend starting from scr...