flow
v1.47.1One development loop - FRAME, BUILD, CHECK, SHIP - replacing separate memory, planning, context, TDD and review frameworks with a single protocol, hard loop guards, and a TDD gate that is enforced by a hook rather than merely instructed.
By Micho CalmaLicense: MIT2 GitHub starsUpdated 2 weeks ago
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Sep 10, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install flow for Codex and Claude Code
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add flow@agent-plugin-marketplacePaste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.
Compatibility: the page URL and API slug “flow-3” remain stable.
- Codex:
flow-3@agent-plugin-marketplace→flow@agent-plugin-marketplace
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/webdevMLC/flow-loopClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/guide/SKILL.md└── skills/loop/SKILL.md
Included Skills2
Write a user guide for the people who will actually use the system — organised by what they are trying to get done, in plain language, in the language they read, with real screenshots of the running product. Offers a reading level and a target language, including bilingual output, and produces a properly laid-out PDF at normal type sizes rather than renderer defaults. Use when a system is going to real users, when support keeps answering the same question, or when the user asks for documentation, a manual, a handbook, or a walkthrough. Walks the running system; never writes a guide from the source code.
The single development loop — brainstorm when the goal is unclear, then FRAME, BUILD, CHECK, SHIP — replacing separate memory, planning, context, TDD, debugging and review frameworks with one protocol. Use for any real feature, fix, refactor, migration, debugging session, or milestone in a project codebase, and equally when the request is still vague and needs shaping before anything gets built. It sizes the task first, fixes the phase order, routes each kind of work to the cheapest model tier that can do it, enforces hard loop guards against repeated research and re-verification, and keeps one state file per project. Can run autonomously without asking when the user explicitly opts in. Not needed for one-off questions or throwaway scratch scripts.
Plugin manifests2
{
"name": "flow",
"version": "1.47.1",
"description": "One development loop - FRAME, BUILD, CHECK, SHIP - replacing separate memory, planning, context, TDD and review frameworks with a single protocol, hard loop guards, and a TDD gate that is enforced by a hook rather than merely instructed.",
"author": {
"name": "Micho Calma",
"url": "https://github.com/webdevMLC"
},
"homepage": "https://github.com/webdevMLC/flow-loop#readme",
"repository": "https://github.com/webdevMLC/flow-loop",
"license": "MIT",
"keywords": [
"skills",
"workflow",
"tdd",
"code-review",
"context",
"planning",
"hooks"
],
"hooks": "./.codex-plugin/hooks.json",
"skills": "./skills/",
"interface": {
"displayName": "Flow",
"shortDescription": "One development loop - FRAME, BUILD, CHECK, SHIP - with enforced TDD",
"developerName": "Micho Calma",
"category": "Productivity"
}
}{
"name": "flow",
"version": "1.47.1",
"description": "One development loop - FRAME, BUILD, CHECK, SHIP - replacing separate memory, planning, context, TDD and review frameworks with a single protocol, hard loop guards, and a TDD gate that is enforced by a hook rather than merely instructed. Ships /flow:ultra, a deep on-demand inspection that runs the system, tests what real flows do to the data, and reviews the code adversarially, then repairs what it found through the loop; /flow:theme, which surveys the interface a project already has, reports what a theme would break before touching a file, then applies one - tokens and a real component layer, rebuilding the native selects, tables, forms, modals and auth pages that make a re-themed UI still look dated; and /flow:guide, which writes a plain-language user guide from the running system, in the reader's own language.",
"author": {
"name": "Micho Calma",
"url": "https://github.com/webdevMLC"
},
"homepage": "https://github.com/webdevMLC/flow-loop#readme",
"repository": "https://github.com/webdevMLC/flow-loop",
"license": "MIT",
"keywords": [
"skills",
"workflow",
"tdd",
"code-review",
"context",
"planning",
"hooks",
"audit",
"data-integrity",
"testing",
"design-system",
"ui",
"theming",
"documentation",
"user-guide",
"localization"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[flow on Agent Plugins Marketplace](https://pluginsmp.com/plugins/flow-3)