problem-decomposerlisted

<!-- Author: jamestexas — drafted by claude-opus-4-7 (2026-05-17) --> # /problem-decomposer — Aspiration → dispatchable lattice Take an aspiration ("ship a platform, not a collection of repos"), descend it through the 5-whys until each branch reaches leaves that satisfy the 7 dispatchability properties (see `DISPATCHABILITY.md`), and emit a structured problem-statement doc + bead specs + non-leaves queue. ## Arguments `$ARGUMENTS` - **`<aspiration-slug>`** — short kebab-case identifier for the aspiration (e.g. `substrate-idl`, `cross-repo-coordination`, `q3-platform-launch`). Becomes the output filename. - **`--input=PATH`** *(optional)* — path to a doc describing the aspiration + relevant context. If omitted, the skill prompts the user (or the orchestrator) for the aspiration text inline. - **`--output-dir=PATH`** *(default: `docs/problems/`)* — where the decomposition doc and bead specs go. - **`--audit=PATH`** *(optional)* — instead of decomposing a new aspiration, audit an existing doc (or bead backlog) for orphan-dispatchable items. See "Audit mode" below. ## Modes ### Decompose mode (default) Take a new aspiration → produce a fresh lattice doc + bead specs. ### Audit mode (`--audit=PATH`) Take an existing decomposition doc, ADR, or bead backlog → check each leaf against the 7 dispatchability properties + the 5-whys chain. Emit a report listing: - Leaves that pass all 7 (good) - Leaves that fail one or more (with which property and why) - Leaves whose "why?" c