flow-work

Execute markdown plans and Beads epics with Git-tracked phase workflows.

674|52|Updated Dec 26, 2025

Search Tags:#epics #Beads #git-workflow #task-tracking #plan-execution #quality-checks

Ready to run

npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-work

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flow-work
Source: https://github.com/gmickel/gmickel-claude-marketplace/tree/main/plugins/flow/skills/flow-work
Command: npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates disciplined execution of plans and Beads epics within a Git-tracked workflow, reducing context drift and ensuring verifiable progress.

Core Features & Use Cases

Plan-driven execution: Load a markdown plan or Beads epic and execute steps in order with git-backed state.
Epic tracking & quality checks: Track progress, enforce task completion, and run tests or lint checks as part of the workflow.
Use Case: When implementing a feature from a spec, load the plan and follow structured phases to complete with tests.

Quick Start

Use the flow-work skill to execute a markdown plan located at plans/<slug>.md or a Beads ID such as gno-40i, following the Phase 1-7 workflow.

Frequently Asked Questions about flow-work

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

FAQPage Schema

How do I execute a markdown plan with Git-backed task tracking?▼

To execute a markdown plan with Git-backed task tracking, load your plan file and follow a phase-based workflow that processes steps in order, enforces completion, and commits progress with traceable state.

What is phase-based plan execution for software feature development?▼

Phase-based plan execution for software feature development is a structured workflow that breaks implementation into sequential phases, enforcing task completion, running quality checks, and committing progress to Git at each stage.

How do I track Beads epics through a Git workflow?▼

You can track Beads epics through a Git workflow by providing a Beads ID as input, which the system processes through structured phases to execute tasks, run tests, and commit verifiable progress with full traceability.

Do I need special setup to run plan-driven task execution alongside Git?▼

No special setup is required to run plan-driven task execution alongside Git beyond having Git installed, as the workflow directly leverages your existing repository state to track progress and commit completed phases.

How does Git enforce quality checks during plan execution?▼

Git enforces quality checks during plan execution by integrating test and lint runs into the phase-based workflow, ensuring tasks pass validation before progress is committed and marked as complete.

What's the best way to prevent context drift when implementing from a spec?▼

The best way to prevent context drift when implementing from a spec is to use a structured plan execution workflow that enforces sequential phase completion, tracks progress in Git, and validates each step before committing.