feature-discoverylisted

# Feature discovery Turns "what should we build next?" into a grounded, ranked roadmap by fanning out many agents instead of one agent guessing. The whole run is a deterministic Workflow script, so every invocation follows the same pipeline rather than being re-improvised. **Distinct from `brainstorm`.** `pm:brainstorm` goes deep on one known-ish feature (interactive Q&A, a single spec doc). This goes wide across the whole product and returns a ranked roadmap of many candidate features. Reach for brainstorm to design *how* to build a chosen feature; reach for this to discover *what* to build. ## When this fits Use it when the user wants ideas that are researched, deduped, specced, and pressure-tested, not a quick off-the-cuff list. It is deliberately heavyweight (roughly 35-40 agents at exhaustive depth), so for a casual "give me three ideas" just answer directly. ## The pipeline (what the script runs) The Workflow engine runs five phases - you do not run these yourself, the engine does (see [scripts/feature-discovery.workflow.js](scripts/feature-discovery.workflow.js)): - **Ground** - one agent maps the current product from the repo (entry points, routes, data models, content, services, config, docs); in parallel a planner proposes competitor segments and one analyst researches each via web search. The product is always mapped, even in `internal` scope, so ideation never re-proposes what exists. - **Ideate** - one agent per value lens (discoverability, core va