book-ddd-distilled-modeling
Guides lightweight domain modeling with ubiquitous language, bounded contexts, and subdomain focus. Always run after every completed grill-with-docs session as an independent second-pass boundary review; also use before PRD, design, or implementation when domain ambiguity exists.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-05
- Stars
- ★ 195
- Forks
- 1
01 前言 Front Matter
- name
- book-ddd-distilled-modeling
- license
- Apache-2.0
- metadata
- { "sbtd.category": "domain", "sbtd.portable": "true", "sbtd.source-revision": "1d82494d74f6df9bca7dccef2da409f87091883e" }
- description
- Guides lightweight domain modeling with ubiquitous language, bounded contexts, and subdomain focus. Always run after every completed grill-with-docs session as an independent second-pass boundary review; also use before PRD, design, or implementation when domain ambiguity exists.
- allowed-tools
- read grep glob bash
- compatibility
- Requires project evidence; Trellis task artifacts and clarification workflows are optional.
02 资源文件 2
03 SKILL.md 正文
Book DDD Distilled Modeling
Use this Skill to sharpen domain language before turning a business request into PRD, issues, design, or code.
It is derived from the mini rule style of agent-rules-books and should run after project evidence is read. It complements grill-with-docs, to-spec, and task planning.
Mandatory Post-grill Review
Every fully completed grill-with-docs session MUST be followed immediately by this Skill, whether the Agent initiated that session or the user invoked it explicitly. The domain-modeling activity embedded in grill-with-docs is the active interview-time modeling pass; it does not satisfy or replace this independent second-pass review.
Re-read the completed clarification result and the supporting project facts. Look for boundary errors, hidden term collisions, unsupported invariants, misplaced responsibilities, and unresolved context ownership rather than merely restating the interview.
The review is a gate before requirement confirmation, PRD, design, task creation, or implementation:
confirmed: no unresolved boundary issue prevents the workflow from advancing.needs-clarification: output the findings, return to one-question-at-a-time clarification, and rerun this Skill after resolution.blocked: the Skill, required evidence, or relevant context is unavailable; output the exact blocker and do not advance.
Invocation origin, a prior domain-modeling pass, or an Agent judgment that the requirement is already clear MUST NOT skip this gate.
When To Use
- Every completed
grill-with-docssession, without exception. - A requirement uses business terms that may mean different things in different parts of the system.
- A change touches domain rules, permissions, lifecycle, workflow state, billing, identity, tenancy, inventory, orders, subscriptions, or similar concepts.
- It is unclear whether two concepts belong in the same model or bounded context.
- A PRD or design needs stable terminology before implementation.
When grill-with-docs was not used, do not use this Skill for purely technical refactors, simple UI copy, mechanical dependency updates, or features with no domain ambiguity.
Workflow
- Read existing project facts first: README, domain docs,
docs/spec, ADRs, task artifacts, and relevant code. - List the key terms and their current meanings in the project.
- Identify bounded contexts where the same word may have different meanings.
- Distinguish core, supporting, and generic subdomains when that affects priority or design.
- State invariants and business rules in the language used by the project.
- Feed the agreed language into
prd.md,design.md, orimplement.md.
Output
Always output the review visibly and separately from the requirement confirmation summary:
DDD Boundary Review
Status: confirmed | needs-clarification | blocked
Ubiquitous language: ...
Bounded contexts: ...
Invariants and business rules: ...
Core / supporting / generic subdomains: ...
Corrections to the grill-with-docs result: ...
Open conflicts and questions: ...
Use not-applicable for a subdomain classification only when it has no bearing on the current decision; do not omit the field. A post-grill review must explicitly state whether it corrected the earlier result, even when the answer is none.
Only stable, cross-task domain decisions should be promoted to docs/CONTEXT.md, ADRs, or docs/spec. Keep the complete review in task-level output or the current prd.md, design.md, or implement.md.
Guardrails
Outside the mandatory post-grill gate, do not force DDD ceremony into small tasks. During the mandatory gate, keep the second pass concise but complete enough to prove the boundaries were independently checked.
04 同仓库更多 Skills
gherkin-bdd
Use when adding, changing, reviewing, testing, synchronizing, or read-only ingesting user-visible behavior with BDD, Gherkin, Given/When/Then scenarios, .feature files, acceptance criteria, knowledge catalogs, or bug-fix behavior specs.
sbtd-workflow-onboard
Checks, installs, or resets SBTD workflow tools, global Skills, managed AGENTS templates, and per-project configuration for local project roots in Oh My Pi.
web-ui-autotest-generator
从前端和后端源码中生成可维护的 Web UI 自动化测试。适用于分析页面、路由、组件、接口、用户流程,生成 Playwright UI 测试,运行测试,生成中文报告,并自检页面功能和跨页面逻辑是否被独立测试资产覆盖。 Generate maintainable Web UI automated tests from frontend and backend source code. Use for analyzing pages, routes, components, APIs, and user flows; generating and running Playwright UI tests; producing Chinese test reports; and checking whether page features and cross-page logic are covered by independent test assets.
seo-geo
SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility, search optimization, search ranking, AI visibility, ChatGPT ranking, Google AI Overview, indexing, JSON-LD, meta tags, or keyword research.
sbtd-task
Use for SBTD task execution and continuation, explicit default/lite/strict mode selection, task records and status changes, cross-session recovery, and task handoffs. Load strict gates only for strict tasks; ordinary questions and read-only work do not create task files.
project-validation
Use after code changes to choose and run validation commands for Node, JavaScript, TypeScript, Python, Go, Dart, Java, Kotlin, C++, Swift, or Objective-C projects. Prefer project-defined commands and report skipped checks and risks.