flow-next-work

Automates e2e execution of Flow epic tasks with built-in validation and reporting.

Updated Jan 15, 2026

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

Ready to run

npx skills add https://github.com/raydocs/inktale --skill flow-next-work-raydocs

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end execution and governance of Flow epics and tasks, ensuring traceable progress and enforced workflow discipline.

Core Features & Use Cases

Enforces Flow discipline using a dedicated .flow/ workspace for task tracking and using flowctl for all state management.
Supports triggering /flow-next:work to bootstrap epics from IDs (fn-N or fn-N.M), spec files, or ideation text.
Maintains rigorous guardrails: mandatory flowctl 'done' confirmations, git staging, and structured evidence per task.
Provides an execution-lead role focusing on plan fidelity and deterministic task progression.

Quick Start

Initialize a Flow epic and start executing its tasks with flowctl, following the phases from input to done.

Frequently Asked Questions about flow-next-work

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

FAQPage Schema

How do I automate epic task execution and enforce workflow discipline in git?▼

Automating epic task execution requires a dedicated .flow/ workspace for tracking and flowctl for state management. This approach enforces mandatory 'done' confirmations, git staging, and structured evidence collection per completed task.

What is the best way to bootstrap epics from spec files or ideation text into actionable tasks?▼

The best way to bootstrap epics from spec files or ideation text is triggering the work command. This initializes the epic, resolves inputs, and progresses phases deterministically from input to done using flowctl.

How does flowctl handle branch management and task validation during epic execution?▼

Flowctl handles branch management and task validation by anchoring context per task, executing phases sequentially, and enforcing strict 'done' verification before allowing progression to the next task in the workflow.

Can I use this automated workflow governance for projects that split epics into multiple sub-tasks?▼

Yes, this automated workflow governance is designed specifically for projects where epics are split into tasks. It applies end-to-end governance from input resolution to completion, ensuring traceable progress and plan fidelity.

Why do I need structured summaries and evidence collection for completed tasks in task management?▼

Structured summaries and evidence collection are needed to maintain rigorous guardrails and traceable progress. They enforce workflow discipline by requiring validation and proof of completion before a task is marked as done.

What are the limitations of manually tracking task progression without a dedicated .flow/ workspace?▼

Without a dedicated .flow/ workspace, manual tracking lacks deterministic task progression and enforced flowctl state management. This leads to missing 'done' confirmations, unverified git staging, and gaps in structured evidence collection.