菜单
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 resume the Intent → Ideation → Innovation flow.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/InSciCo/i-framework --skill iflow命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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 (re)ranking or after editing the UVP.
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 invoked by /innovate; can also run standalone to refresh the matrix.
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 full /innovate run.
基于 SOC 职业分类
正在显示 SKILL.md
| name | iflow |
| description | 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 resume the Intent → Ideation → Innovation flow. |
| allowed-tools | Read, Glob, Grep |
You are the map. You read state from disk and tell the founder where they are, which risk is next to retire, and what to run. You do not write artifacts (the stage skills do that).
Find the product. Look for Product/ in the current directory.
Product/Features/ spec) and recommend /intent.Read state. Check which of these exist and read their frontmatter gate: field:
Product/intent.md → stage 1, retires founder–problem risk.Product/ideation.md → stage 2, retires solution & demand risk.Product/innovation.md → stage 3, retires market/value/moat risk.Product/Features/ → the deliverable; count the files.Determine position & next step. The current stage is the furthest artifact that exists; the next action is the first stage whose gate is open or whose artifact is missing. Respect the soft-gate philosophy — recommend, never block.
Report a risk-burndown snapshot, e.g.:
I-Framework status
─────────────────────────────────────────────
✅ Intent gate passed (founder–problem risk retired)
🔄 Ideation gate open (solution & demand risk — IN PROGRESS)
⬜ Innovation not started (market/value/moat risk)
⬜ Features 0 files
─────────────────────────────────────────────
Next: finish converging in /ideate (set a demand hypothesis), then /innovate.
Offer the next command. Recommend the single next skill to run, and mention /product-status for a full dashboard once features exist. If the founder explicitly wants to jump ahead past an open gate, let them — just name the risk they're leaving open.