菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | robo-tasks |
| description | 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. |
| extends | speckit-tasks |
| requires-speckit | >=0.8.13, <0.9.0 |
| user-invocable | true |
This skill inherits the workflow of /speckit-tasks. Before executing
anything else, read .claude/skills/speckit-tasks/SKILL.md and treat its
Outline + Task Generation Rules as the default behavior. Then apply
the Overrides section below on top.
If the installed speckit version is outside the requires-speckit range
declared in the frontmatter above, warn the developer explicitly in
your first reply and ask for confirmation before continuing.
TODO (US2 — T035): replace this section with the override list per research R11. Outline:
- Before generating any task: call MCP
compute_driftwith the element ids +nameSeenvalues referenced by the localplan.md. Ifstatus == "drift"and any blocking category is non-empty, stop and report; do not write tasks against stale names (FR-013).- Task format: every checkbox item MUST include exactly one HTML-comment marker of the form
<!-- @robo elementId="..." kind="Aggregate|Command|Event|ReadModel" item="..." -->, placed at the end of the line for the checkbox. The marker keys the task to a design element so checkbox state can be reflected on the Design tab (FR-007 / FR-008).- Marker scope: markers go in
tasks.mdonly. Never instruct the LLM to write marker comments into developer source code —/robo-implementis explicitly forbidden from doing so (research R7), and/robo-syncuses full AST extraction instead.
See specs/029-robo-spec-skills/data-model.md §2.3 for the marker shape and contracts/mcp-tools.md for the MCP surface.
컨텍스트 간 상호작용을 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). 기존 전략 메모리를 재사용한다.
