Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By cofin
Implements a structured Context-Driven Development workflow with spec-first planning, TDD execution, and Beads integration for managing flows, tasks, and knowledge across AI-assisted coding sessions.
npx claudepluginhub cofin/flow --plugin flowArchive completed flows + elevate patterns
Re-assess, reorganize, and optimize project context for implementation-readiness
Five-phase documentation workflow
Complete flow work - verify, review, merge/PR/keep/discard
Execute tasks from plan (context-aware)
Review Flow specs, plans, and implementation changes for correctness, risk, and missing verification.
Execute Flow implementation tasks with TDD, Beads notes, verification, and sync discipline.
Generate zero-ambiguity Flow specs and implementation worksheets after codebase analysis.
Analyze broad goals and produce Flow PRD roadmaps with implementation-ready child flows.
Use when running AlloyDB Omni locally or outside GCP, configuring container deployments, Kubernetes operators, RPM installs, columnar engine tests, or local development that needs AlloyDB behavior.
Use when provisioning Google AlloyDB, configuring clusters or read pools, enabling columnar engine, setting up Private Service Access, tuning managed PostgreSQL on GCP, or migrating from Cloud SQL to AlloyDB.
Use when editing Angular projects, angular.json, *.component.ts files, @Component code, signals, standalone components, control-flow blocks, Angular migrations, or Angular version-specific APIs.
Use when work depends on current external API behavior, SDK docs, framework versions, breaking changes, migration guides, changelogs, release notes, deprecations, or syntax that may have changed.
Use when evaluating architecture, component boundaries, coupling, cohesion, abstractions, large refactors, new layers, maintainability risks, or design choices with long-term structural consequences.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This plugin requires configuration values that are prompted when the plugin is enabled. Sensitive values are stored in your system keychain.
useBeadsUse Beads (bd) for task persistence. Disable to run in degraded mode without bd.
${user_config.useBeads}agentsDirDirectory where Flow stores specs, plans, and knowledge (e.g. .agents or specs)
${user_config.agentsDir}Opinionated 6-phase development lifecycle for Claude Code — language-agnostic, repo-local bin/* delegation
SPEC-First development workflow with TDD, Ralph Loop, and autonomous agent coordination for Claude Code
End-to-end development workflow: design → draft-plan → orchestrate → review → pr-create → pr-review → pr-merge
Persona-driven AI development team: orchestrator, team agents, review agents, skills, slash commands, and advisory hooks for Claude Code
Research-backed orchestration for Claude Code. Structured workflow from idea to production with parallel execution, session memory, 70-point validation, autonomous mode, and adversarial review. 51 commands, 15 agents across 7 departments.
Context-Driven Development framework for Claude Code
Measure twice, code once.
Flow is a unified toolkit for Context-Driven Development that works with Claude Code, Gemini CLI, Codex CLI, OpenCode, VS Code / Copilot, Cursor, Google Antigravity, and OpenClaw. It combines spec-first planning with Beads for persistent cross-session memory, enabling AI-assisted development with deep, persistent project awareness.
Control your code. By treating context as a managed artifact alongside your code, you transform your repository into a single source of truth that drives every agent interaction. Flow ensures a consistent, high-quality lifecycle for every task:
Lifecycle: Context → Spec & Plan → Implement → Learn
Each host has a native plugin/extension system. Use it. The tools/install.sh script is a multi-host orchestrator for users who want to install Flow across several CLIs at once — it just runs the same native commands for you.
gemini extensions install https://github.com/cofin/flow --auto-update
Update with gemini extensions update flow. Use gemini extensions link . only for local development against a checkout — Gemini copies installed extensions, so linked development and installed releases are different workflows.
Flow's gemini-extension.json already sets plan.directory: ".agents" so enter_plan_mode / exit_plan_mode write the approval artifact under Flow's canonical .agents/specs/ directory. You only need to enable planning + model routing yourself:
{
"general": {
"plan": {
"enabled": true,
"modelRouting": true
}
}
}
Do not rely on undocumented autoEnter behavior for model routing.
claude plugin marketplace add cofin/flow
claude plugin install flow@flow-marketplace
This installs Flow at user scope (~/.claude/plugins/...). Restart Claude Code after install. The plugin ships skills, commands, and hooks; Claude-specific subagents remain optional and are not bundled in the current release.
claude plugin marketplace update flow-marketplace
claude plugin update flow@flow-marketplace
Claude Code does not let plugin authors pre-declare a plan-artifact directory the way Gemini does. To get the equivalent behavior — plan-mode artifacts written under Flow's canonical .agents/specs/ directory — set this in your project .claude/settings.json:
{
"plansDirectory": ".agents/specs"
}
Optionally, force plan mode by default for Flow projects:
{
"permissions": {
"defaultMode": "plan"
}
}
Verify the keys against your Claude Code version's settings reference.
codex plugin marketplace add cofin/flow
Then in a Codex session, run /plugins and enable Flow. Update with codex plugin marketplace upgrade flow-marketplace.
Codex CLI 0.117+ supports first-class marketplace commands — add accepts owner/repo[@ref], HTTPS/SSH git URLs, or local paths, with optional --ref <REF> and --sparse <PATH>.
Codex plugins do not currently expose plugin-defined
/flow:*slash commands. Use Flow through the installed Flow skill with natural-language requests such asUse Flow to set up this project.
Codex CLI has no plugin-author hook for a plan-artifact directory. The closest Gemini-equivalent knob is reasoning effort for plan mode — set in your ~/.codex/config.toml:
plan_mode_reasoning_effort = "high"