Iflow

Skill InSciCo/i-framework/.claude/skills/iflow

A Claude Code plugin that turns a startup idea into a build-ready product spec through Intent, Ideation, and Innovation.

Install

npx -y skills add InSciCo/i-framework --skill iflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.3 KB, as published. Nobody here has run it

/iflow — orchestrator & router

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

Procedure

Find the product. Look for Product/ in the current directory.
- Absent: this is a fresh start. Explain the flow (Intent → Ideation → Innovation → a 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.