Can I use Flow-Work with custom plan files?

Absolutely. You can point the skill to any Markdown plan file located in your project's plans directory (e.g., /flow:work plans/feature.md) to start systematic implementation.

What is a Beads ID in the context of Flow-Work?

Beads IDs (e.g., bd-123) refer to specific issue identifiers within the Beads project management system. Flow-Work can fetch these issues and execute them as structured plans.

What happens if I don't have rp-cli installed?

Flow-Work automatically checks for rp-cli. If it's not found, the skill skips the review-specific setup questions and focuses on branch management and plan execution.

Is testing mandatory during the workflow?

Yes. Flow-Work includes guardrails that prevent skipping tests or leaving tasks half-done, ensuring the implementation strictly adheres to the provided plan.

Does this skill support isolated git worktrees?

Yes. During the mandatory setup phase, you can choose to work in your current branch, a new branch, or a completely isolated git worktree to keep your environment clean.

Flow Work: Systematic Plan Execution

Name: Flow Work: Systematic Plan Execution
Author: gmickel

bygmickel

•

356

Productivity & Workflow

Executes technical plans and epic issues systematically with automated git workflows, task tracking, and quality gates.

About

Flow Work is an execution-focused Claude Code skill designed to transform detailed plans or issue IDs (like Beads) into completed codebases with high fidelity. It enforces a structured workflow by guiding users through initial setup—including branch management and review preferences—before systematically moving through implementation phases. By integrating with tools like RepoPrompt and Beads, it ensures that every step of a plan is followed, tested, and reviewed, preventing context drift and ensuring production-grade output for complex engineering tasks.

Key Features

356 GitHub stars
Mandatory setup gate for branching and multi-model review strategies
Automated Git workflow management including branches and isolated worktrees
Phase-based execution tracking to prevent half-finished tasks or skipped tests
Integrated quality checks and Carmack-level implementation reviews via rp-cli
Systematic execution of Markdown plan files and Beads issue IDs

Use Cases

Managing long-running coding tasks that require structured tracking and multi-model review gates
Implementing complex features from a pre-defined technical specification or plan file
Executing specific tasks or issues directly from the Beads project management system

About

Key Features

356 GitHub stars
Mandatory setup gate for branching and multi-model review strategies
Automated Git workflow management including branches and isolated worktrees
Phase-based execution tracking to prevent half-finished tasks or skipped tests
Integrated quality checks and Carmack-level implementation reviews via rp-cli
Systematic execution of Markdown plan files and Beads issue IDs

Use Cases

Managing long-running coding tasks that require structured tracking and multi-model review gates
Implementing complex features from a pre-defined technical specification or plan file
Executing specific tasks or issues directly from the Beads project management system