flow-next-work

To orchestrate epics and tasks with git-backed tracking, this workflow uses flowctl to coordinate task creation, status checks, and commits. It enforces a structured execution model to ensure repeatable progress and prevent drift.

Preventing workflow drift when executing development epics requires a disciplined, git-tracked execution model. By enforcing deterministic task handoff to worker subagents and applying flowctl, the workflow maintains repeatable progress from spec to completion.

To start a workflow from a markdown spec or an idea-based start, you provide an epic or task identifier. The workflow reads SKILL.md frontmatter and executes phases from phases.md, guiding the process through optional branch choices and review modes.

Yes, this task management workflow supports spec-driven epics, markdown-started epics, and idea-based starts. It orchestrates all task scenarios defined by a Flow epic, coordinating task creation and optional completion reviews via the Flow CLI.

Yes, you can use flowctl for task management with worker delegation in DevOps environments. The workflow applies deterministic task handoff to standalone worker subagents, ensuring structured execution and optional completion reviews.

When applying Ralph-mode handling in automation workflows, the system enforces specific guardrails to maintain deterministic task handoff. These guardrails ensure structured worker-based execution and prevent unmanaged drift during epic completion.