agentsclimarketplace
Sign in

Iflow

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

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.From its SKILL.md

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.

One thing to look at

  • 4 stars4 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.

SKILL.md

2.3 KB, 463 tokens by cl100k_base, 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

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

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

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

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

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.