flow-next-work

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.

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.

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.

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.

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.

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.