Plan the domain breakdown of the project from global specifications and identify what domain-level documents should exist before detailed domain spec generation.
This skill creates a domain expansion plan from the global specification layer.
Use this skill when the user wants to:
Do not use this skill for:
Read these files first:
specs/global/*specs/ref/*docs/PRD.md.codex/modules/PRD-Pipeline/rules/doc-scope.md.codex/modules/PRD-Pipeline/rules/summary-sync.mdAlso read references/domain-plan-contract.md.
Create or update a domain planning document that includes:
Default output:
specs/domains/summary.mdIdentify modules, responsibilities, extension points, and cross-domain dependencies.
Choose domain boundaries that reduce ambiguity while staying proportional to project complexity.
For each domain, specify whether it needs:
SA.mdlayer-core.mdlayer-dao.mdlayer-biz.mdlayer-facade.mdRecommend which domains should be expanded first and why.
For each domain, note whether the downstream spec should stay light, balanced, or deep. Domains that directly affect runtime correctness, persistence, public contracts, or validation should default to deeper treatment.
Before finishing, verify: