Commands

Every DevArch command has a moment it's meant for. Reach for them when the situation below shows up — and when you're not sure, /devarch:guide maps them all.

Starting & shaping a project

/devarch:brainstorm: When you have a rough idea or overview. Turns it into focused requirements and decisions through iterative Q&A.
/devarch:domain-model: When the domain is complex — rich rules, multiple bounded contexts. Forges the ubiquitous language before code is written.
/devarch:ddd-assessment: When you're unsure how much modeling a project needs. Measures domain complexity and recommends what to turn on.
/devarch:sources: When you have raw material — event-storm photos, transcripts, sketches. Registers and extracts them into modeling candidates.

Understanding an existing codebase

/devarch:architect-review: When you inherit or revisit a codebase. Grades it across the categories an architect actually cares about.
/devarch:adr-review: Before building on decisions captured as ADRs. Checks them for gaps and cross-decision conflicts.
/devarch:plan-review: After planning a non-trivial goal, before you implement. Checks every phase against your ADRs, profile, and notation — and flags any step that contradicts a decision you already made. Runs automatically after planning.
/devarch:dashboard: Anytime you want a status snapshot — code health, test health, plans, and open blockers in one page.

Every session

/devarch:recap: At the start of a session. Recovers what was done last time, where things stand, and what's next.
/devarch:standup: When you want a quick read on progress — done, next, blockers, plus DevArch lifecycle state.
/devarch:finalize: When you're ready to commit and push. Writes a work summary, stages it, commits, and pushes.
/devarch:guide: When you're not sure which command fits. The map of every DevArch skill and where it belongs in the lifecycle.