Skip to content
Skills Library
Programming · Planning

flow

/flow

Use when a repository has .agents, when the user asks for Flow lifecycle routing, OKF v0.2 bundle task tracking, spec-driven planning, TDD implementation, status, learn/resynthesize, review, finish, archive, or /flow:* help.

Author
cofin ↗
Repository
flow ↗
Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
19
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Use when a repository has .agents, when the user asks for Flow lifecycle routing, OKF v0.2 bundle task tracking, spec-driven planning, TDD implementation, status, learn/resynthesize, review, finish, archive, or /flow:* help.

Original author description

Use when a repository has .agents, when the user asks for Flow lifecycle routing, OKF v0.2 bundle task tracking, spec-driven planning, TDD implementation, status, learn/resynthesize, review, finish, archive, or /flow:* help.

How it works

  1. Trigger
  2. Workflow
  3. Guardrails
  4. Output
  5. Validation
  6. References
Original SKILL.md headings · 59 lines, 397 words
SKILL.md preview
---
name: flow
description: "Use when a repository has .agents, when the user asks for Flow lifecycle routing, OKF v0.2 bundle task tracking, spec-driven planning, TDD implementation, status, learn/resynthesize, review, finish, archive, or /flow:* help."
---

# Flow Router

<!-- lifecycle-ownership: owner=flow; operations= -->

## Trigger

Use Flow when `.agents/` exists (in the workspace or linked primary Git worktree), 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` &rarr; [`flow-setup`](../flow-setup/SKILL.md) ([`references/setup.md`](references/setup.md), [`multi-harness-plugins`](../multi-harness-plugins/SKILL.md))
- `prd` | `spec` (alias `plan`) | `revise` (alias `refine`) | `research` (alias `task`) &rarr; [`flow-planning`](../flow-planning/SKILL.md) ([`references/prd.md`](references/prd.md), [`references/spec.md`](references/spec.md), [`references/revise.md`](references/revise.md), [`references/research.md`](references/research.md))
- `implement` | `status` &rarr; [`flow-execution`](../flow-execution/SKILL.md) ([`references/implement.md`](references/implement.md), [`references/status.md`](references/status.md))
- `learn` (aliases `resynthesize`, `refresh`, `sync`) &rarr; [`flow-learn`](../flow-learn/SKILL.md) ([`references/learn.md`](references/learn.md), [`multi-harness-plugins`](../multi-harness-plugins/SKILL.md))
- `docs` | `pr` &rarr; [`flow-docs`](../flow-docs/SKILL.md) ([`prose-and-documentation.md`](../flow-docs/references/prose-and-documentation.md), [`agent-context.md`](../flow-docs/references/agent-context.md), [`prs-commits-and-changelogs.md`](../flow-docs/references/prs-commits-and-changelogs.md))
- `review` | `finish` | `archive` | `cleanup` | `revert` | `validate` &rarr; [`flow-completion`](../flow-completion/SKILL.md) ([`references/review.md`](references/review.md), [`references/finish.md`](references/finish.md), [`references/archive.md`](references/archive.md), [`references/cleanup.md`](references/cleanup.md), [`references/revert.md`](references/revert.md), [`references/validate.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.
- Keep 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`) synchronized in place in present tense ([`references/state.md`](references/state.md)), validating OKF writes with `/flow:validate`.
- Scale process and models proportionally ([`skills-subagents-and-mcp-limits.md`](../multi-harness-plugins/references/skills-subagents-and-mcp-limits.md)): call shipped packaged workflows (`flow-scout`, `flow-spec-planning`, `flow-chapter-pipeline`, `flow-dual-review`) with `type_name="self"` on Google Antigravity, restrict `haiku`/`flash_lite` strictly to narrow (`<= 3`-file) fetches, surface an explicit warning whenever `planning_quality: degraded` indicates a spec was not planned on the primary frontier thinking model, batch edits across each active chapter with a single fast (`< 60s`) lint + targeted unit gate, and never mark chapters or tasks `deferred` without `deferred_by: "user"`.
- In linked `git worktree` checkouts, reuse the symlinked `.venv` via `uv run --no-sync` (never run `make install` unless dependencies changed); edit worktree `.agents/` when `ignore_policy` is `shared`, and edit the primary checkout's `.agents/` when `local-only`.
- 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

- [Archive](references/archive.md)
- [Cleanup](references/cleanup.md)
- [Discipline](references/discipline.md)
- [Finish](references/finish.md)
- [Implement](references/implement.md)
- [Interaction](references/interaction.md)
- [Learn](references/learn.md)
- [PRD](references/prd.md)
- [Research](references/research.md)
- [Revert](references/revert.md)
- [Review](references/review.md)
- [Revise](references/revise.md)
- [Setup](references/setup.md)
- [Spec](references/spec.md)
- [State](references/state.md)
- [Status](references/status.md)
- [Studio](references/studio.md)
- [Validate](references/validate.md)
Files in this package (19)
  • SKILL.md 5 KB
  • references/archive.md 5 KB
  • references/cleanup.md 3 KB
  • references/discipline.md 12 KB
  • references/finish.md 6 KB
  • references/implement.md 16 KB
  • references/interaction.md 8 KB
  • references/learn.md 10 KB
  • references/prd.md 5 KB
  • references/research.md 7 KB
  • references/revert.md 3 KB
  • references/review.md 11 KB
  • references/revise.md 4 KB
  • references/setup.md 15 KB
  • references/spec.md 11 KB
  • references/state.md 9 KB
  • references/status.md 2 KB
  • references/studio.md 6 KB
  • references/validate.md 6 KB

Versions

RepositoryScoreLicence
This page · cofin/flow90Apache-2.0
lifecycle-innovations-limited/claude-ops100MIT
manhquydev/flow-skill100MIT
simota/agent-skills100MIT
justinedevs/meta-architect100MIT
cofin/flow100Apache-2.0
panayiotism/claude-harness100MIT
Panza-Labs/floorboss96Apache-2.0
ohdearquant/lionagi95Apache-2.0

Database snapshot: 13.11.2026 · package version ba5d0af97421 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100flow-completion
    Use when reviewing (/flow:review), finishing (/flow:finish), archiving (/flow:archive), cleaning up (/flow:cleanup), reverting (/flow:revert), or validating (/flow:validate) Flow work.
  • 90flow-learn
    Use when reorienting across machines or harnesses (/flow:refresh), reconciling spec checklists (/flow:sync), auditing codebase or spec drift, sharpening domain glossaries and ADRs, or resynthesizing OKF v0.2 knowledge and .agents/skills/ (/flow:learn, /flow:resynthesize).
  • 100flow-next-spec-completion-review
    Spec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review.
  • 100planning
    High-level development planning — features, TDD, architecture review. Triggers on: plan, feature, architecture, design, TDD, strategy.
  • 100spec-flow
    Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview. NOT for generic…
  • 100flow-next
    Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for building or planning work (use flow-next-flow).

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.