菜单
Unified domain and data modeling for business entities, invariants, schema design, aggregate boundaries, and evolution strategy. Use when designing business models, schema changes, bounded contexts, or consistency rules.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Lightweight implementation orchestrator for low-complexity work — fixes, refactors, doc changes, or single-AC features that do not warrant a phase plan or factory decomposition.
Linear phase-loop orchestrator for single-feature implementation plans. Use for medium-complexity work where transparent human-in-the-loop phase review is preferred over factory automation.
Implementation entry point. Use to execute a completed specification. Auto-detects the decomposition tier (Direct, Incremental, or Factory) from spec artifacts and dispatches to the matching execution sub-skill.
Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is preferred over factory automation.
Scaffold, status-check, and manage specification directories. Use when creating a new spec, reading spec status, transitioning between phases, or logging decisions on a spec in .start/specs/.
Create a comprehensive specification from a brief description. Runs requirements gathering, solution design, and decomposition — routing decomposition to one of three tiers based on a complexity classifier: Direct (no plan), Incremental (linear phase plan), or Factory (parallel units with holdout scenarios).
| name | domain-modeling |
| description | Unified domain and data modeling for business entities, invariants, schema design, aggregate boundaries, and evolution strategy. Use when designing business models, schema changes, bounded contexts, or consistency rules. |
Act as a domain-modeling specialist who aligns business concepts, data structures, and consistency boundaries into an implementation-ready model.
Modeling Target: $ARGUMENTS
DomainModel { boundedContexts: string[] entities: string[] valueObjects: string[] aggregates: string[] invariants: string[] persistenceStrategy: string schemaDecisions: string[] migrationPlan: string[] }
State { target = $ARGUMENTS concepts = [] constraints = [] model = {} }
Always:
Never:
reference/strategic-patterns.md — Bounded contexts, context mapping, ubiquitous languagereference/tactical-patterns.md — Entities, value objects, aggregates, domain events, repositoriesreference/consistency-strategies.md — Transactional (ACID), eventual consistency, saga pattern