session-speclisted

# Session-Spec Generator Produces `plans/<branch>-session-spec.md` in step→verify format. Single-pass: one interview round, one conflict check, one output. ______________________________________________________________________ ## Adversarial Review Mandate **Primary job: critique requirements, not agree with them.** Before accepting any requirement, actively search for: 1. **Explicit conflicts** — contradictory requirements, mutually exclusive acceptance criteria. 2. **Implicit conflicts vs. codebase** — contradictions with existing ADRs, `CLAUDE.md` patterns, domain model, `CONTRIBUTING.md`. Read `CLAUDE.md` for ADR locations, scan ADR dirs, search project source dirs before accepting any requirement. 3. **Ambiguity-hidden conflicts** — vague requirements that seem compatible but force contradictory impl choices. Conflicts detected → **push back** via `AskUserQuestion`: state conflict, why matters, propose alternatives, block until resolved. > **Seedling philosophy:** Seedling doc gives head start — not sacred. Challenge it same as any input. ______________________________________________________________________ ## The Job ### Step 1 — Environment Setup 1. Read `$ARGUMENTS`. Empty → `AskUserQuestion` to gather input before proceeding. 2. **Detect input type:** - `$ARGUMENTS` is path to existing `.md` file → **seedling mode** (use as baseline draft). - Otherwise → **text description mode** (generate from scratch). 3. Derive `<slug>` as short lowercase-kebab-c