ddt-large-requirementlisted

# Decomposing Large Requirements Into Briefs Help turn a large, multi-module requirement into a fully formed set of `docs/requirements/` + `docs/briefs/` + global-layer design artifacts under `docs/design/` + global decisions through natural collaborative dialogue. Start by understanding the current project context and the full handoff materials, then ask questions one at a time to refine the scope, module boundaries, and decomposition. Once you understand what's in (and out of) scope, present the requirements acceptance, the brief list, and the global-layer design artifacts, and get user approval. <HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented the requirements + briefs + global-layer design artifacts and the user has approved them. This applies to EVERY large requirement regardless of perceived simplicity. Do NOT invoke ddt-brainstorming on individual briefs until the global-layer ddt-design-checkpoint passes. </HARD-GATE> ## What Goes Into `docs/design/` At The Global Layer `docs/design/` is not an "ADR-only" folder. It holds **anything about the design intent that you cannot read off the code**, at the global / cross-slice layer: - **Architecture** — module topology, layered structure, dependency graph - **Cross-slice business flows** — how a user / data / event travels across multiple briefs - **Cross-slice sequence diagrams** — message ordering, timing-sensitive in