flow-prime

Configure FLOW workspace permissions, install bin/* stubs, and set up pre-commit hooks.

25|3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/benkruger/flow --skill flow-prime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-prime
Source: https://github.com/benkruger/flow/tree/main/skills/flow-prime
Command: npx skills add https://github.com/benkruger/flow --skill flow-prime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This setup handles the one-time initialization required when starting or upgrading FLOW projects. It configures workspace permissions, applies the necessary Git excludes, installs the bin/* delegation stubs, and writes a version marker so the feature workflow can initialize reliably.

Core Features & Use Cases

  • Initializes workspace permissions and project config for FLOW to ensure secure, repeatable setups.
  • Installs bin/* delegation stubs and creates a version marker to enable /flow:flow-start and subsequent commands.
  • Sets up repository state and pre-commit hooks to enforce FLOW-driven commits and project hygiene.

Quick Start

Run the prime setup to initialize FLOW workspace permissions, install bin/* stubs, write the version marker, and configure excludes and hooks.

Frequently Asked Questions about flow-prime

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure workspace permissions for a new FLOW project?

To configure workspace permissions for a new FLOW project, run a one-time prime setup that applies Git excludes, installs bin/* stubs, and writes a version marker to enable immediate feature development.

What is the purpose of a pre-commit hook in FLOW workflow automation?

A pre-commit hook in FLOW workflow automation enforces project hygiene and FLOW-driven commits by validating repository state before changes are finalized, ensuring repeatable and secure setups.

How do I set up bin/* delegation stubs for my repository?

Setting up bin/* delegation stubs requires running the FLOW prime setup, which automatically installs the stubs and writes a project config to enable /flow:flow-start and subsequent workflow commands.

Do I need to run prime setup every time I upgrade FLOW workflows?

Yes, you need to run prime setup every time you upgrade FLOW workflows because it writes a version marker and updates the .flow.json config to ensure the feature workflow initializes reliably.

What's the best way to initialize project config and enforce Git excludes for FLOW?

The best way to initialize project config and enforce Git excludes for FLOW is executing the one-time prime setup, which configures workspace permissions, writes .flow.json, and prepares the environment for feature development.

Why does /flow:flow-start fail to initialize after installation?

/flow:flow-start fails to initialize if the one-time prime setup has not been run to install bin/* stubs, write the version marker, and configure the necessary workspace permissions and hooks.