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:objective: When you've committed to an outcome someone outside engineering will judge. Captures what must become true, by when, and what would falsify it, then makes you record the baseline before the work starts, because once it does the 'before' state stops being observable.
/devarch:brainstorm: When you have a rough idea or overview. Turns it into focused requirements and decisions through iterative Q&A.
/devarch:test-coverage-assessment: When you adopt an existing repo and need to know how much state-changing behavior is actually verified, not how many lines execute. Runs the project's own tooling, grades assertion quality, and keeps findings in a committed store.
/devarch:proposal: When you have a punch list, a Jira story or set of stories, or PRD-derived work in hand. Facilitated intake: asks what's included, gives every item a checkable outcome, and tracks per-item acceptance. From a story it copies the outcome sentence and bullets in verbatim, downloads the attachments, and sends a non-conforming story back as questions.

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:adr-interview: When an ADR carries open questions. Resolves them one at a time (each answer folds into the record immediately), then runs the review and offers acceptance when the last one falls.
/devarch:proposal-review: Before accepting a proposal's items. Checks each item against your ADRs and tracked work, flagging contradictions, duplicates, unplannable items, and decisions in disguise. Runs automatically after intake.
/devarch:plan-review: After planning a non-trivial goal, before you implement. Checks every phase against your ADRs, profile, and accepted proposals, 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:team-standup: When the repo runs in team mode and you want the whole team's picture: every developer's session stream rolled up, with blocker classes that hit more than one dev flagged. Read-only; one dev's arc with a user argument.
/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.

Setting up your environment

/devarch:add-tools: When a session needs something the machine doesn't have yet: PDF text, image conversion, diagram rendering, media. Pick from a menu your project curates, installed one at a time and verified after each.
/devarch:add-api-key: When work needs a service API key. Stores it at .api-keys/{service}-key with the gitignore entry written before the key itself, so it cannot be committed, even transiently, and it's never echoed back.