Results for “product-idea”

Transforms vague ideas into structured, actionable concepts through guided divergent and convergent thinking, producing a markdown one-pager.

Orchestrator for the pre-decision business-idea lifecycle — generate ideas, model them, evaluate them, validate them with customers, and only then hand off to product-soul / brainstorming. Routes through `idea-generation`, `business-modeling`, `idea-evaluation`, and `customer-discovery`. Load when the user asks to explore business ideas, find a startup idea, evaluate a venture, validate an idea, says "what business should I start", "should I build this", "is this a good business", "I have a startup idea", "evaluate this venture", "model this business", "validate this idea", "Mom Test this", "Lean Canvas this", "Business Model Canvas", "Value Proposition Canvas", "go/no-go on this idea". Pre-decision suite — once one idea is committed, hands off to `product-soul`. Does NOT design features (use `brainstorming`) or audit built products (use `reality-check`).

Shape a rough product or project idea into a scoped brief before customer discovery, market research, specifications, UX, UI, or implementation planning

Identify risky assumptions for a new product idea across 8 risk categories including go-to-market, strategy, and team.

Launch new products from idea to first customers using frameworks for positioning, outreach, and experimentation.

Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning to decide whether it deserves investment or recommendation.

Turns a raw idea into four linked planning files through a five-phase pipeline: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with kill criteria.

Turns a raw feature or project idea into a structured product plan document covering goals, audience, requirements, and constraints, with a maturity-tracking workflow.

Creates concise early UX discovery artifacts for PRD development, customer development, new product ideas, feature bets, and redesigns. Use when the user asks to hypothesize an ideal customer profile, generate proto-personas, write customer problem or jobs-to-be-done hypotheses, create journey maps, shape value propositions, or turn product context into design-sprint-style customer insight artifacts for product and engineering teams.

Synthesize customer research data to define the Ideal Customer Profile (ICP) including demographics, behaviors, Jobs to Be Done, and pain points.

Translates high-level ideas into detailed Epic-level Product Requirements Documents (PRDs) that serve as the single source of truth for engineering teams.

Identify what to measure, test, or track to de-risk a product or AI idea across internal and external risk dimensions.

Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders.

Pressure-test any business idea with a five-angle adversarial panel (Critic, Champion, Analyst, Investigator, Customer) that returns a single GO/RESHAPE/KILL verdict with the cheapest test to de-risk it.

Runs focused experiments to validate feasibility of an idea, saving artifacts to .planning/spikes/ and supporting both idea and frontier modes.

Design lean startup experiments (pretotypes) for a new product by creating XYZ hypotheses and suggesting low-effort validation methods like landing pages, explainer videos, and pre-orders.

PRD Creation

Stress-test a feature idea for an existing product by surfacing risky assumptions across Value, Usability, Viability, and Feasibility using multi-perspective devil's advocate thinking.

Turns a raw idea, brain dump, or conversation into a complete PRD with mandatory acceptance criteria and measurable success metrics. Extracts the problem, target users, and jobs-to-be-done, runs a quick competitive scan (web if available, logged as a gap if not), drafts the full PRD (problem, personas, user stories.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday.

Plan customer discovery interviews with the right goal, segment, constraints, and method for problem validation, churn research, or new product ideas.

Turns product ideas into structured specs for AI tools or stakeholder review, with quick feature specs and full project scopes.

Turns a brief product idea into working, verified code by orchestrating requirements analysis, planning, parallel implementation, QA, and multi-perspective validation.

Rank a backlog of feature ideas by impact, effort, risk, and strategic alignment to identify the top 5 to pursue.

Creates an outcome-backed product strategy memo from an Ideal Customer Profile markdown file, pasted ICP notes, discovery artifacts, product context, or PRD context. Use when asked to create product strategy, convert an UX Discovery and ICP into strategy, define vision-to-outcome strategy, turn discovery into strategic bets, clarify target customer outcomes, evaluate roadmap strategy, or avoid feature-factory planning.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", "de-risk before building", "GV sprint", "prototype testing", or "design workshop". Also trigger when a team needs to make a critical product decision quickly, resolve stakeholder disagreements, or test risky ideas before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.

Run customer interviews that uncover real problems using Mom Test rules: ask about their life, not your idea; focus on past specifics; and secure commitments instead of collecting compliments.

Create or maintain STRATEGY.md - the product's target problem, approach, users, key metrics, and tracks of work. Use when starting a new product, updating direction, or when prompts like 'write our strategy', 'update the roadmap', 'what are we working on', or 'set up the strategy doc' come up. Also triggers when ce-ideate, ce-brainstorm, or ce-plan need upstream grounding and no strategy doc exists yet.

Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.

Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less. Use when the user mentions "customer interviews", "validate my idea", "users say they want it but dont buy", "leading questions", "The Mom Test", "customer feedback bias", or "interview script". Also trigger when preparing user research questions, interpreting ambiguous customer feedback, or designing customer discovery processes that avoid false positives. Covers commitment and advancement, avoiding compliments, and extracting signal from noise. For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint.