feature-discovery

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):

• 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 value, UX, monetization, engagement, trust, information architecture), each grounded in the inventory and competitor findings, each forbidden from proposing anything that already exists.
• Shortlist - a single curator merges duplicates, drops the trivial and the already-built, ranks by value-to-effort, and picks the top 8-12 (5-6 at depth: quick).
• Spec & Validate - a pipeline per feature: spec it, then an adversarial skeptic scores novelty, real value, feasibility in the current architecture, competitor precedent, and maintenance burden, returning build / maybe / drop with a confidence score.
• Synthesize - one agent writes the final Markdown report: exec summary, gaps (internal and versus competitors), a ranked roadmap table, full specs for the build/maybe features, dropped ideas with reasons, and a quick-wins-vs-bigger-bets split.