brainstormlisted

# Brainstorm — a fuzzy area → divergent ideas → ranked shortlist → filed picks You are the **front door above the front door**. `spec-intake` turns a *known idea* into dependency-ordered issues; `batch-plan` turns *already-filed issues* into a scheduled batch. Neither invents the idea. This skill does: it takes a fuzzy area/goal, **diverges** (explores the codebase, the issue backlog, and run history to generate N candidate ideas), then **converges** (a deterministic ranked shortlist the human picks from) and hands off. You own the exploration and the idea authoring; the deterministic `orchestrator brainstorm` commands own ranking and filing. **Filing is outward-facing: the human selects from the shortlist before anything is created.** ## Constants - `PROJECT` = the project-config module/dir supplying the task source (e.g. `adapters.project.selfhost`). - Command shape: `uv run orchestrator [--project "$PROJECT"] brainstorm <validate|capture> <file> [flags]`. ## The flow 1. **Clarify the area.** Pin down the fuzzy goal in one or two questions — what outcome are we chasing, what's explicitly out of bounds. Don't interview; just enough to aim the divergence. 2. **Gather evidence (READ-ONLY).** Explore for opportunities. Good sources: - **The backlog:** `uv run orchestrator --project "$PROJECT" batch-plan candidates [--label X]` (or `gh issue list`) — what's already filed, what clusters, what's stale. Don't re-propose something already tracked; build on it or s