Assess or re-assess the innovation-vs-implementation classification and 0-100 innovation weight for one feature or the whole Product/Features set, then regenerate the ranked features-index.md and run the portfolio sanity check. Use when features need…
Stage-3 companion for the I-Framework. Research the competitive landscape with live web search and build a sourced product comparison matrix in Product/competition.md, then read off the whitespace, the table-stakes, and where rivals beat you. Optionally…
Create or revise a single Product feature file with a complete user story, Given/When/Then acceptance criteria, and an innovation-vs-implementation classification. Use when adding one feature to Product/Features/, or refining an existing feature, outside a…
Stage 2 of the I-Framework. Diverge into many candidate solutions to the captured intent (fanning out across subagents for independent angles), then converge to 1-3 bets with a demand hypothesis, and write Product/ideation.md. Use after /intent.
The front door / orchestrator for the I-Framework. Reads the Product/ folder, determines which stage (Intent, Ideation, Innovation) you're in from the artifacts and their gates, reports the risk-burndown state, and routes you to the next step. Use to start or…
Stage 3 of the I-Framework. Pressure-test the chosen bet for differentiation and moat, define the UVP, then decompose it into a complete feature set written to Product/Features/ with each feature classified innovation vs implementation. Produces the…
Stage 1 of the I-Framework. Run a guided interview to capture a founder's intent — the problem, the target user, why-now and why-us, and evidence of real pain — then write Product/intent.md. Start here when defining a new startup or product idea.
Render a read-only dashboard of the Product/ folder — stage/gate completion, risk-burndown state, feature counts by classification and priority, the ranked innovation edge list, and gaps (UVP elements with no feature, features missing acceptance criteria,…