sdd-orchestrate-prdslisted

# Orchestrate SDD PRDs A broad request becomes a set of slices: each slice has one primary outcome, its own PRD, and a TechSpec that fits without branching. The user approves the slicing before any PRD exists on disk. 1. **Understand the request and fix the prefix.** Gather objective, users, journeys, surfaces, integrations, constraints and declared out-of-scope. Consult local evidence before public sources and mark each obligation as fact, assumption or product decision. Derive the prefix in kebab-case from the request's domain, or use `--prefix` when supplied. List existing `tasks/prd-[prefix]-*` and reuse the matching slug when the scope coincides. **Output:** prefix resolved, obligations inventoried with their origin, and already-written slices identified; ask only for the missing information that blocks the inventory. 2. **Design the slicing.** Group the obligations by cohesion: one primary outcome per slice, minimal coupling between slices, and a scope one TechSpec covers within a single subsystem. Separate independent journeys, distinct surfaces and layers deliverable in different orders; keep together whatever shares a contract and would fail alone. Assign each cross-cutting obligation (authentication, observability, NFR) to one owning slice and cite it as a constraint in the others. Number in dependency order and name each slug `[prefix]-[NN]-[slice]`. **Output:** every obligation from step 1 belongs to exactly one slice; each slice has a single primary outco