robo-architect

컨텍스트 간 상호작용을 Event/Command/Query 로 분류하고 pub/sub vs 동기 결합을 결정하며 결합 위험을 점검하는 Connect 스테이지(ddd-starter Step 5).

Discover 이벤트를 도메인 용어 서브도메인으로 묶고 책임·인접관계·느슨한 결합을 점검하는 Decompose 스테이지(ddd-starter Step 3).

영향 BC 마다 Bounded Context Canvas(책임·입출력·유비쿼터스 언어·비즈니스 결정)를 작성하는 Define 스테이지(ddd-starter Step 7). 기존 메모리의 언어를 재사용한다.

Proposal 변경이 도입/영향을 주는 도메인 이벤트를 시간 순으로 펼치고 Pivotal Event·Hotspot·외부시스템을 식별하는 Discover 스테이지(ddd-starter Step 2).

Detailed DDD 모드 진입 시 Proposal 의 영향 범위를 분류해 어떤 ddd-starter 스테이지를 적용/생략할지 stagePlan 을 제안한다.

영향 서브도메인을 Core/Supporting/Generic 으로 분류하고 차별성·build-vs-buy 를 판단하는 Strategize 스테이지(ddd-starter Step 4). 기존 전략 메모리를 재사용한다.

BCC 에서 Aggregate 경계·불변식·상태전이·명령/이벤트·처리량을 도출하는 Tactical 스테이지(ddd-starter Step 8 + robo-proposal-plan 전술 규칙).

Robo Architect-aware implementation loop. Inherits speckit-implement; constrains file placement to the layout dictated by plan.md, ticks tasks.md checkboxes as work completes, registers scaffolded files in the graph via MCP, and never writes marker comments into developer source code.

Robo Architect-aware planning. Resolves a feature-id / BC / Aggregate argument via the robo-spec MCP bridge, drafts plan.md with classification-driven architecture (clean for core, default speckit for supporting), and never emits spec.md / data-model.md / contracts/ — those live in the Robo Architect graph.

Reverse sync — propagates developer-made edits to aggregate / event / command properties in source code back into the Robo Architect graph via AST extraction (no marker comments). Propose→confirm→apply (Principle IV); destructive changes (renames, deletions) require explicit confirmation.

Robo Architect-aware task generation. Inherits speckit-tasks; every checkbox item carries an HTML-comment marker mapping it to a Robo Architect design element so checkbox state can be reflected on the Design tab.

Robo Architect-aware implementation loop. Inherits speckit-implement; constrains file placement to the layout dictated by plan.md, ticks tasks.md checkboxes as work completes, registers scaffolded files in the graph via MCP, and never writes marker comments into developer source code.

Robo Architect-aware planning. Resolves a feature-id / BC / Aggregate argument via the robo-spec MCP bridge, drafts plan.md with classification-driven architecture (clean for core, default speckit for supporting), and never emits spec.md / data-model.md / contracts/ — those live in the Robo Architect graph.

Reverse sync — propagates developer-made edits to aggregate / event / command properties in source code back into the Robo Architect graph via full AST extraction (no marker comments). Propose→confirm→apply (Principle IV); destructive changes (renames, deletions) require explicit confirmation.

Robo Architect-aware task generation. Inherits speckit-tasks; every checkbox item carries an HTML-comment marker mapping it to a Robo Architect design element so checkbox state can be reflected on the Design tab.