Flow setup

Skill cofin/flow/plugins/flow/skills/flow-setup

Context-Driven Development toolkit for AI agents — spec-first planning, TDD workflow, and Beads integration.

Install

npx -y skills add cofin/flow --skill flow-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when initializing Flow in a repo, configuring .agents, installing or checking Beads bd, setting local-only sync policy, or creating first project context files.

SKILL.md

2.1 KB, 440 tokens by cl100k_base, as published. Nobody here has run it

Flow Setup

Use this lifecycle skill for project initialization, installation checks, setup validation, and first context files.

Beads mode: Skip every bd invocation when the SessionStart hook reports Beads Backend: Missing (None) or Disabled via plugin config (useBeads=false). Treat spec.md markers as fallback source of truth and skip /flow:sync. Never halt for missing Beads. See ../flow/references/discipline.md.

Workflow

Detect project root, existing .agents/ state, Beads availability, and repo-native commands.
If Beads is missing, offer official Beads (bd) installation or no-Beads degraded mode.
Initialize Flow context files from templates and prefer local-only Beads settings.
Store setup decisions in Beads notes when a backend exists.
Re-run setup validation before handing off to planning.

Guardrails

Prefer .git/info/exclude for local-only ignores.
Do not edit .gitignore unless the user wants shared repository policy.
Do not run bd dolt push, bd export, or auto-stage unless policy explicitly allows it.
Keep setup idempotent; preserve existing user context files and merge rather than overwrite.

Validation

Confirm .agents/ root, workflow.md, patterns.md, knowledge/index.md, and Beads config existence when setup is expected.
Confirm Beads config defaults are local-only: no git ops, no auto export, and no auto git add.
Run repository validation commands documented in .agents/workflow.md or hook context.

References Index

Example

User: "Use Flow to set up this repo."

Action: detect the repo root, initialize .agents/, configure local-only Beads, capture setup notes, validate files, then hand off to flow-planning for the first flow.

Gives 0 of the 12 instructions most project setup skills give in 440 tokens

Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-06

ask one question at a timein 29 of 999, across 28 files
detect the package manager from lockfilesin 28 of 999, across 9 files
present findings to the userin 25 of 999, across 4 files
explore current repo statein 24 of 999, across 3 files
update the agent skills block in place if it existsin 24 of 999, across 3 files
install husky lint-staged and prettierin 23 of 999, across 4 files
create the lintstagedrc filein 22 of 999, across 3 files
commit all changed filesin 22 of 999, across 3 files
run lint-staged to verify it worksin 22 of 999, across 3 files
initialize huskyin 21 of 999, across 2 files
create the husky pre-commit filein 21 of 999, across 2 files
create a prettierrc file if missingin 21 of 999, across 2 files

Said here and by no other author read

detect project root and existing setup state
offer beads installation or degraded mode
initialize flow context files from templates
prefer local-only beads settings
store setup decisions in beads notes
re-run setup validation before handoff

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.