agentleFS
InSciCoInSciCo/i-framework/.claude/skills/iflow/SKILL.md

iflow

Skill4 starsChanged 4 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Find the product: Look for Product/ in the current directory.

    line 13
  2. Very specific:

    Read state: Check which of these exist and read their frontmatter gate: field:

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.