flow-next-work

Orchestrate Flow epics and tasks with git-based tracking and quality gates.

674|52|Updated Dec 26, 2025

Search Tags:#automation #git #workflow #quality-assurance #task-management #epic #flowctl

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flow-next-work helps engineering teams execute a Flow epic or task in a disciplined, auditable manner by managing git state, task tracking, and quality gates.

Core Features & Use Cases

Deterministic task lifecycle with flowctl, including staged commits and explicit done checks.
Git-aware task tracking and task-scope management across epics and tasks.
Mandatory quality gates and reviews, with a bundled flowctl script and strict completion checks.
Flexible workflow modes and reproducible execution context via worker subagents.

Quick Start

Invoke the skill with a Flow epic or task reference, for example: /flow-next:work fn-1-add-oauth. The system will guide you through branch choices and review configuration, then spawn a worker to implement tasks.

Frequently Asked Questions about flow-next-work

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

FAQPage Schema

How do I enforce quality gates and track git state when implementing epics and tasks?▼

You can enforce quality gates and track git state during epic and task implementation by using deterministic execution flows with mandatory completion checks and git-based task tracking to maintain plan fidelity and ensure auditable reviews.

What is the best way to orchestrate task lifecycles with deterministic state management?▼

Orchestrating task lifecycles deterministically requires a bundled flowctl script that manages staged commits, explicit done checks, and reproducible execution contexts via worker subagents to guarantee auditable task tracking.

How do I start working through a specification across multiple tasks using a worker subagent?▼

Start working through a specification by invoking the skill with a Flow epic or task reference, which guides you through branch choices and review configuration before spawning a worker subagent to implement the tasks.

Does this task management approach work without prior dependencies or external components?▼

Yes, this task management approach works without prior dependencies or external components, relying solely on its bundled flowctl script and git-based tracking to coordinate epic and task execution.

Why do I need strict completion checks for workflow automation and task-scope management?▼

Strict completion checks are needed for workflow automation and task-scope management because they enforce mandatory quality gates and reviews, preventing unreviewed work from advancing and ensuring deterministic execution across epics.

When should I not use git-based task tracking for epic and task implementation?▼

Git-based task tracking for epic and task implementation is not suitable when your workflow requires flexible execution without mandatory quality gates, as this approach enforces deterministic state management and strict completion checks.