agentleFS
Sign inStart free
cofincofin/flow/skills/flow-setup/SKILL.md

flow-setup

Skill19 starsChanged 5 days agoApache-2.0View on GitHub

Use when initializing or aligning Flow in a repository, migrating legacy .agents/ layouts, scaffolding OKF v0.2 knowledge bundles, or generating baseline and domain .agents/skills/ and .agents/agents/.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. flooooooooooow/flow-skills★ 1same name
    2. Indrajitvp/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use for /flow:setup. Follow ../flow/references/setup.md.

    line 13
  2. Very specific:

    Create Flow's core context chapters with bounded <= 40-line <!-- truth: start --> blocks and zero body --- separators: product/product.md, …

    line 23
  3. Very specific:

    Follow ../multi-harness-plugins/SKILL.md and ../flow-docs/references/agent-context.md.

    line 26
  4. Very specific:

    Ask once via structured-choice-v1 whether .agents/ is shared (tracked in Git, Recommended) or local-only (stealth mode via …

    line 30
  5. Very specific:

    Never copy Flow's global plugin skills (flow, flow-*, okf, debloat, multi-harness-plugins) or legacy flow-memory-keeper into …

    line 35
  6. Very specific:

    Every materialized knowledge chapter must cite real repository paths (path/to/file::Symbol) in sources: and [^id] footnotes.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Flow Setup

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

Trigger

Use for /flow:setup. Follow ../flow/references/setup.md.

Workflow

  1. Environment Detection, Brownfield Alignment, & Sharded Toolchain Discovery:
    • Inspect .agents/setup-state.json and .agents/bundles/index.md. If .agents/ already exists, offer Align & True-Up (Recommended), Full Re-Setup, or Exit.
    • In alignment/brownfield mode, inventory legacy layouts (.beads/, .agents/specs/, .agents/tracks/, .agents/transactions/, flat knowledge/patterns.md, sibling PRD child specs with parent_prd: if desired, un-promoted bundles/research/, legacy .agents/skills/flow-memory-keeper/), ensure subdirectory index.md files and log.md carry zero YAML frontmatter and zero standalone --- body rules, and migrate active work without data loss after user confirmation.
    • Probe installed host binaries (uv, python3, cargo, go, bun, pnpm, npm, make, just, pwsh, powershell) alongside repository manifests. Fan out parallel read-only @researcher subsystem Scouts (type_name="self" with agents/researcher.md on Google Antigravity; model="inherit").
  2. Scaffold Core Context Chapters & Rich OKF v0.2 Bundle (.agents/bundles/):
    • Initialize .agents/bundles/index.md (okf_version: "0.2") and frontmatter-free .agents/bundles/log.md, product/index.md, knowledge/index.md, research/index.md, and specs/index.md.
    • Create Flow's core context chapters with bounded <= 40-line <!-- truth: start --> blocks and zero body --- separators: product/product.md, product/product-guidelines.md, product/tech-stack.md, and knowledge/workflow.md (populated with verified host commands from ../../templates/agent/workflow.md).
    • Synthesize evidence-backed nested chapters across knowledge/{architecture,patterns,domains,testing,gotchas,decisions}/ (via parallel domain synthesis subagents when >= 2 domains exist) with sources: [{ id, resource, title }] + [^id]: footnotes and verified: [{ by, at }].
  3. Seed Baseline Engineering Disciplines & Stack-Specific Project-Local Skills (.agents/skills/) and Subagents (.agents/agents/):
    • Follow ../multi-harness-plugins/SKILL.md and ../flow-docs/references/agent-context.md.
    • Embed baseline engineering rules into the repository's knowledge and skill set: Deep-Module & Seam Design, Active Domain Modeling & ADR Filter, Public-Seam Vertical-Slice TDD & Hypothesis-Driven Bug Diagnosis, and Present-Tense Cold-Reader Prose & Documentation Accuracy.
    • Generate consolidated domain skills (.agents/skills/<domain>/SKILL.md <= 200 lines + references/*.md), domain review capability skills (.agents/skills/review-<domain>/SKILL.md + references/checklist.md + references/false-positive-suppressions.md), .agents/skills/index.md, and paired project-local subagents (.agents/agents/<domain>-reviewer.md and .agents/agents/<domain>-specialist.md with H1 # headings, mainAgent: false, subagent: true, model: inherit, and commandExecutionPolicy: sandbox).
  4. Cross-Harness Policy & Stop Hook Bootstrap, AGENTS.md, & .agents/setup-state.json:
    • Ask once via structured-choice-v1 whether .agents/ is shared (tracked in Git, Recommended) or local-only (stealth mode via .git/info/exclude).
    • Offer opt-in non-destructive harness policy and project-local SessionStart + Stop hook merges (.claude/settings.local.json with backup, .cursor/hooks.json, opencode.json), update root AGENTS.md (preserving <!-- project-customization: start --> blocks), and write .agents/setup-state.json.

Guardrails

  • Never copy Flow's global plugin skills (flow, flow-*, okf, debloat, multi-harness-plugins) or legacy flow-memory-keeper into .agents/skills/.
  • Every materialized knowledge chapter must cite real repository paths (path/to/file::Symbol) in sources: and [^id] footnotes.
  • Preserve existing custom content inside <!-- project-customization: start --> and <!-- truth: start --> blocks during alignment.

Output

Return the initialized or aligned .agents/bundles/ tree, generated .agents/skills/ and .agents/agents/ inventory, verified host commands, and next command (/flow:spec or /flow:prd).

Validation

Confirm root index.md declares okf_version: "0.2", all links in index.md and .agents/skills/index.md resolve on disk, every non-reserved .md file has valid OKF frontmatter, and .agents/setup-state.json records setup_status: "complete".

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free