Sdd Orchestrate Prds

---
name: sdd-orchestrate-prds
description: Slice SDD when a broad request must become several cohesive PRDs under a shared prefix; for a single PRD, use sdd-create-prd.
argument-hint: --prompt "broad description" [--prefix common-slug]
disable-model-invocation: true
---

# 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. This session writes every PRD; subagents are read-only explorers.

1. **Understand the request and fix the prefix.** Gather objective, users, journeys, surfaces, integrations, constraints, and declared out-of-scope items. 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]-*` folders and reuse the matching slug when the scope coincides. If one of them holds an `active` `context-snapshot.md`, load it through the Load branch of `.agents/skills/sdd-snapshot/SKILL.md` and resume from its next step; a slicing it records as approved is not asked again unless the request changed.
   **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 (configuration, observability, NFR) to one owning slice and cite it as a constraint in the others. Number the slices in dependency order, continuing from the highest number already used under `tasks/`, and name each slug `[NN]-[prefix]-[slice]`.
   **Output:** every obligation from step 1 belongs to exactly one slice; each slice has a single primary outcome; dependencies between slices form an order without cycles. A single slice is a valid result when the request has one primary outcome.
3. **Approve the slicing.** Present each slice with slug, outcome, covered obligations, and dependencies. Use the available question tool (`AskUserQuestion`) or, without it, a textual question carrying the same options, each naming the slugs it produces: the proposed slicing, a more granular alternative, and a more grouped one. Rely on the automatic "Other" option for the user to type whatever split they want, including a different prefix. Remap the obligations onto the chosen split and ask again only when it leaves an obligation without an owner or creates a cycle.
   With more than one slice, write the snapshot with `sdd-snapshot` in the first slice's folder right after approval, recording the approved slugs, outcomes, owned obligations, and the user's answer as `now` decisions, so a later session end cannot lose the slicing.
   **Output:** slicing approved in the conversation, remapped onto the inventory, and recorded in the snapshot; no PRD on disk until that answer.
4. **Draft each slice.** For each approved slice, in dependency order, follow `.agents/skills/sdd-create-prd/SKILL.md` in this session with the final slug, that slice's obligations and evidence, the sibling slugs as boundaries, and the instruction to record cross-slice dependencies under `Constraints and dependencies` and boundaries under `Out of scope`. Load only that slice's obligations and cited sources before drafting it. Read-only explorers may gather evidence for several slices in parallel; this session writes every PRD.
   After each slice except the last, run the session pause from `session-continuity.md` with stage `planning` and the next slice as next step; a written snapshot moves to the next slice's folder and the previous one is marked `superseded`.
   **Output:** each approved slice has `tasks/prd-[NN]-[prefix]-[slice]/prd.md` written, or a blocker with a concrete cause that stops only that slice.
5. **Check the set and report.** Check coverage against step 1's inventory, unique IDs within each PRD, each functional requirement appearing in a single slice, and dependencies declared on both sides. Correct a divergence in the owning slice's PRD before reporting. Report paths, the suggested order for `sdd-create-techspec`, and pending items inherited from the PRDs. Mark the snapshot `closed`, or point its next step at the first slice's TechSpec when the user continues.
   **Output:** reviewable set on disk; obligations without an owner and repeated requirements resolved or explicitly pending.

Read each source once per version. When a request extends an existing prefix, preserve the written PRDs and treat the new scope as additional slices starting from the next free number. Under `sdd-orchestrate-flow`, the flow runs the session pause and records the slicing in `workflow.md`.