flow-next-work

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.

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.

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.

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.

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.

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.