skills/flow-setup/SKILL.md
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.
npx skillsauth add cofin/flow flow-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this lifecycle skill for project initialization, installation checks, setup validation, and first context files.
Beads mode: Skip every
bdinvocation when the SessionStart hook reportsBeads Backend: Missing (None)orDisabled via plugin config (useBeads=false). Treatspec.mdmarkers as fallback source of truth and skip/flow:sync. Never halt for missing Beads. See../flow/references/discipline.md.
.agents/ state, Beads availability, and repo-native commands.bd) installation or no-Beads degraded mode..git/info/exclude for local-only ignores..gitignore unless the user wants shared repository policy.bd dolt push, export, or auto-stage unless policy explicitly allows it..agents/ root, workflow.md, patterns.md, knowledge/index.md, and Beads config existence when setup is expected..agents/workflow.md or hook context.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.
development
Use when tracing execution paths, mapping dependencies, understanding unfamiliar code, following data flow, investigating end-to-end behavior, debugging call chains, or deciding which files to read next.
development
Use when reviewing authentication, authorization, user input, secrets, API keys, database queries, file uploads, session management, external API calls, OWASP risks, or data handling attack surface.
testing
Use when analyzing tradeoffs, comparing approaches, weighing options, assessing risks, stress-testing conclusions, identifying blind spots, or applying multiple viewpoints to a decision.
development
Use when reviewing hot paths, slow code, database queries, N+1 risks, memory usage, loops, I/O, caching strategy, concurrency, latency-sensitive paths, or resource efficiency.