SuperAPI AI Directory

ddd-scope

General & other

View repository

Updated 10-16 02:31

About this skill

DDD Scope

English version: English

When to Use

  • Requirements are vaguely described, and different roles have inconsistent understanding of the problem boundaries.
  • Before a brand-new project starts, the modeling scope, constraints, and key risks need to be locked down.
  • When a subsequent Skill reports "unclear business value proposition," re-execute as a backtracking target.

Input Requirements

  • Required: Business objectives or problem description (unstructured text is allowed: oral accounts, PRD fragments, ticket descriptions are all acceptable).
  • Optional: Current system form, key participants, external system dependencies, known constraints (time/compliance/performance/team).

Process

  1. Extract business intent to form a 1-sentenceproblem statement(describing the pain point) and a 1-sentencevalue statement(describing the expected outcome).
  2. Clarifygoalsandnon-goals, establish scope boundaries—explicitly state "what will not be done."
  3. Listconstraints and assumptions, marking each as "verifiable / non-verifiable" and the verification method.
  4. Generate aterm seed list: extract nouns, verbs, and state words from the description, marking ambiguity points and the scenario they belong to.
  5. Identify arisk list: cover business risks, integration risks, data consistency risks, and delivery risks, and provide preliminary mitigation suggestions.
  6. Output anext-step preparation checklist: the minimum information, participating roles, and expected outputs required to enter ddd-discover .

Output

Artifact Structural Requirements
Problem statement and value statement 1 sentence each, acceptable to the business side
Goals / Non-goals In list form, each item includes a boundary explanation
Constraints and assumptions Table: constraint/assumption, verifiability, verification method
Term seed list Table: term, definition candidate, ambiguity point, scenario
Risk list Table: risk, impact, trigger condition, mitigation suggestion
Next-step preparation checklist List: roles, necessary inputs, expected outputs

Verification Checklist

  • Goals and non-goals are mutually exclusive and executable
  • Constraints and assumptions are all marked with verification methods
  • Term seeds ≥ 10, ambiguity points are marked
  • The risk list covers all four categories: business / integration / consistency / delivery
  • The problem statement and value statement do not contain technical implementation details

Backtracking Triggers

This Skill is the system entry point and does not trigger backtracking. However, in the following cases, backtracking will be triggered by downstream to this point:

  • ddd-subdomains Unable to distinguish core domain from supporting domain → the business value proposition is unclear, and scope needs to be re-converged.

Example

@ddd-scope
业务描述:我们的订单售后流程非常混乱,跨系统协同困难,客户投诉响应慢。
请帮我收敛为 DDD 建模输入:输出问题陈述、目标/非目标、约束与假设、术语种子、风险清单。