idea

Refine an idea into idea.md: $ARGUMENTS

/idea is the front door of the PRD-creation flow (PM phase) — upstream of /create-prd and the existing pipeline. It ingests one source, refines it through a grill, and writes a lean one-page idea.md (per ${CLAUDE_PLUGIN_ROOT}/references/idea-format.md) that seeds the Product Requirements Document. It is not a PRD: no code change. Output lands in the PRD folder the key names, on the first write and never relocated. It then vendors what it read into that same folder (Phase 4.5) so the record the specs repo keeps is one whose links resolve for everybody, not only for the operator whose disk the sources came off.

Flags: --deep switches the grill from bounded (≤10 questions) to relentless (until convergence). --no-docs turns off documentation grounding (see Phase 1). --ground-code [<repo>[,<repo>…]] grounds the idea against mounted code (see Phase 2.6) — bare it derives the repo set, with a value it scans exactly those repos. The token after --ground-code is its value only when it contains no whitespace and every comma-separated part matches a top-level directory basename under ${REPOS_PATH:-/workspace}; otherwise the flag is bare and the token is idea text.

Phase 0 — Resolve the address + model routing

1. The address (mandatory). Parse the first non-flag token and validate it with key-valid (${CLAUDE_PLUGIN_ROOT}/references/addressing.md §1). Absent or malformed → stop: IDEA_NEEDS_KEY: /idea needs a PRD key (^[A-Z][A-Z0-9_]*(-\d+)+$, e.g. ACME-77) — it names the folder this idea will live in. Re-run '/dev-workflows:idea <PRD-KEY> [<prompt>|@<file>]'.

   The key is an argument because there is nowhere keyless to write. idea.md lands in its final folder on the first write — PRD-<KEY>-<slug>/ under $SPECS_PATH/specifications/, resolved with resolve-address and created there when absent (addressing.md §2, §3). It is never relocated afterwards, and /create-prd <KEY> finds it there.

   Validated for shape and checked against nothing, exactly as /brd-intake <BRD-KEY> already asks. Nothing looks a key up, because there is nothing to look it up in.

   Accepted cost: an abandoned idea leaves a folder in specifications/. Reintroducing a staging area to avoid that would restore the relocation step this removes.

2. Resolve model routing. Invoke the model-routing skill (Skill tool, skill: "dev-workflows:model-routing"), then record:

   model_routing:
     classification: MODERATE          # idea refinement is typically MODERATE
     reason: <one-line>
     current_model: <the model this orchestrator/grill is running under>
     detection_model: <§2.1 Sonnet chain: claude-sonnet-5, fallback claude-sonnet-4-6/4-5>   # idea-reader
     authoring_model: <= current_model>   # the interactive grill + idea.md authoring (session model, not a delegated subagent)
     opus_available: <true if a §2 Opus model resolved, else false>
     notes: <any §2/§2.1 fallback or degradation>
   

   The grill + authoring run inline on current_model (the §2 Opus chain — interactive judgment, not a delegated subagent). idea-reader runs on detection_model. If no Opus resolves, degrade to the best available and record the degradation in notes and the final report — do NOT hard-block (a PM must not be blocked from capturing an idea by a momentary Opus outage). A --ground-code run does not floor the classification at SIGNIFICANT: §1.1's multi-source floor is written for /implement, and §8.3's purpose — the strongest available model on synthesis — is already met here, because the grill and authoring run inline on current_model while the scanners run on detection_model.

Specs-repo preflight. Cite ${CLAUDE_PLUGIN_ROOT}/references/specs-repo-git.md and execute its specs-preflight entry point (§3) inline: flush any leftover session artifacts from an earlier run, retry an artifact commit that failed to push, and settle the branch. Prompt-free and silent when the specs repo is clean and on its default branch. If a guard fires, emit its §5 notice; if it returns specs_git: blocked (§3.3 G0), carry that flag for the whole run — the terminal commit-artifacts step skips on it.