flow skill
✓ VerifiedRoutes agent requests to specific lifecycle skills for managing project stages like planning, implementation, documentation, and completion.
- GitHub stars
- 20
- Files
- 19
- Last commit
- Nov 8, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the flow skill do?
flow routes agent requests to specific lifecycle skills for managing project stages like planning, implementation, documentation, and completion.
Summary generated from the skill's SKILL.md.
About the flow skill
Managing complex software development lifecycles through structured agent workflows is what flow enables. Developers use this skill when a repository contains an .agents directory or when they need to navigate specific project stages like planning, implementation, or documentation. Instead of performing direct disk mutations, the router identifies the correct lifecycle skill and reference procedure required for the task at hand.
An agent should load this skill to route requests to specialized subagents such as flow-planning for spec-driven planning, flow-execution for implementation and status updates, or flow-docs for documentation tasks. It relies on a directory structure containing spec bundles under .agents/bundles/specs/ and maintains synchronization across root specifications, chapter catalogs, and task worksheets. This approach keeps the coordinator efficient by scaling horizontally across isolated subagents while preserving Git history and tag immutability.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the flow skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the flow skill in Plugin
/plugin marketplace add cofin/flow /plugin install flow@flow-marketplace
Install the flow skill in Claude Code
~/.claude/skills/flow/SKILL.md
$ npx degit cofin/flow/skills/flow ~/.claude/skills/flowInstall the flow skill in Claude Code (project)
.claude/skills/flow/SKILL.md
$ npx degit cofin/flow/skills/flow .claude/skills/flowInstall the flow skill in Codex
~/.agents/skills/flow/SKILL.md
$ npx degit cofin/flow/skills/flow ~/.agents/skills/flowInstall the flow skill in Gemini CLI
~/.gemini/skills/flow/SKILL.md
$ npx degit cofin/flow/skills/flow ~/.gemini/skills/flowInstall the flow skill in Claude.ai
npx degit cofin/flow/skills/flow flow && zip -r flow.zip flow # claude.ai → Customize → Skills → + → Create skill → Upload a skill → flow.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablecofin/flow/skills/flow is public and reachablegithub.com/cofin/flow/tree/HEAD/skills/flow ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-08github.com/cofin/flow/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/cofin/flow/blob/HEAD/skills/flow/SKILL.md ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/cofin/flow/blob/HEAD/skills/flow/SKILL.md ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 63 linesgithub.com/cofin/flow/blob/HEAD/skills/flow/SKILL.md ↗Pass
SKILL.md
View on GitHubFlow Router
Trigger
Use Flow when .agents/ exists, spec bundles live under .agents/bundles/specs/, or the user requests a Flow action. Flow is a skill and subagent workflow, not a shell executable; never run flow as a shell command.
Workflow
Route the requested operation directly to its owning lifecycle skill:
setup→flow-setup(references/setup.md,multi-harness-plugins)prd|spec(aliasplan) |revise(aliasrefine) |research(aliastask) →flow-planning(references/prd.md,references/spec.md,references/revise.md,references/research.md)implement|status→flow-execution(references/implement.md,references/status.md)learn(aliasesresynthesize,refresh,sync) →flow-learn(references/learn.md,multi-harness-plugins)docs|pr→flow-docs(prose-and-documentation.md,agent-context.md,prs-commits-and-changelogs.md)review|finish|archive|cleanup|revert|validate→flow-completion(references/review.md,references/finish.md,references/archive.md,references/cleanup.md,references/revert.md,references/validate.md)
The router owns no disk mutations directly; it resolves the target lifecycle skill and reference procedure immediately.
Guardrails
- Load only the selected lifecycle skill and its reference procedure.
- Root specifications (
specs/<flow_id>/spec.md), chapter catalogs (chapters/index.md), chapter specs (chapters/<ch_id>/spec.md), and task worksheets (tasks/<id>-<slug>.md) are kept synchronized in place in present tense—stating current verified state, remaining chapters, and the full plan without historical sediment (references/state.md). - Keep the coordinator thin (
< 25kexploration tokens) by scaling horizontally across isolated subagents: on Google Antigravity, userun_workflow(phase(),parallel(),pipeline(),agent(..., type_name="self", schema=..., model="inherit")) orinvoke_subagent(TypeName="self", Model="inherit", ...)bound toagents/<role>.mdcontracts for sharded scouts, upfront parallel chapter authoring (ch01..chNN,1–4tasks/chapter, zero upper cap), per-chapter zero-context reviews, single-chapter task execution, and OKF/doc synthesis. - Preserve Git history and tag immutability. Never push or open remote PRs without explicit user instruction.
Output
Identify the selected lifecycle skill and reference procedure and execute the requested stage.
Validation
Confirm one lifecycle owner matches the requested operation and that the active harness loads the corresponding skill and reference document.
References
Files in this skill
19flow skill questions
How do I install the flow skill in Claude Code?
Run npx degit cofin/flow/skills/flow ~/.claude/skills/flow. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the flow skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How do I trigger the Flow skill?
Flow is triggered when a .agents/ directory exists, spec bundles are found under .agents/bundles/specs/, or a user explicitly requests a Flow action.
Can I run flow as a shell command?
No, Flow is a skill and subagent workflow rather than a shell executable; you should never attempt to run it as a shell command.
Which skill handles the implementation and status tracking stages?
The implement and status operations are routed to the flow-execution skill.