Launch the DDD Architecture Coach. With no argument, shows an in-flight summary derived from {coachoutputroot}/ and asks which BC to focus on. With a BC name, derives the next phase for that BC and enters it. Use this as the default entry point.
Append a learning to .claude/arch-learnings.md. Pass the learning content as the argument; the coach writes it with source=usertriggered and the appropriate appliesto scope.
Force entry into Phase 1 (Domain Discovery). Skips state-based phase selection. Use when you explicitly want to (re-)run scenario modeling, event/command extraction, BC delineation, classification, touchpoint map, AI opportunities, or User Stories. With no argument → system-level Steps 1–5. With a BC name → per-BC…
Force entry into Phase 2 (Architecture Design) for one BC. Requires explicit BC argument. Use when you want to (re-)work on Context Map, per-BC architecture decisions, cloud deployment, or AI-ADRs for a specific BC.
Force entry into Phase 3 (Implementation Specification) for one BC. Produces aggregate definitions, key examples (Gherkin), test specs, slice plan. Requires explicit BC argument.
Force entry into Phase 4 (Review & Iterate). Reviews any phase or BC artifact against five health checklists (DDD / AI / Engineering / Cloud / SBE) and produces scored findings. Optional scope argument (Phase 1 / Phase 2 / Phase 3: / / system / full); no argument runs full review.
★not rated 5 4mo agoA72 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: