flow-work

Coordinate end-to-end task execution from epic plans using flowctl and git tracking.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/raydocs/antiflowskills --skill flow-work-raydocs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-work
Source: https://github.com/raydocs/antiflowskills/tree/main/.factory/skills/flow-work
Command: npx skills add https://github.com/raydocs/antiflowskills --skill flow-work-raydocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates end-to-end software task execution from planning to completion, enforcing a consistent workflow that uses a central task store (.flow) and git-based state tracking to reduce drift and improve traceability.

Core Features & Use Cases

  • Deterministic orchestration from epic to task with .flow/ tracking.
  • Git-integrated status, evidence, and history for each task.
  • Guardrails and checks to ensure mandatory steps (plan, epic, tasks, and done state) are followed.
  • Use cases include implementing a plan, executing a spec, or delivering features from an epic.

Quick Start

Implement the epic-to-task flow by answering setup questions and following the Phase-driven workflow to complete all tasks with flowctl and git commits.

Frequently Asked Questions about flow-work

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

FAQPage Schema
How do I automate epic-to-task workflow execution for software development?

Automate epic-to-task workflow execution by using flowctl to link epic plans to individual tasks, enforcing mandatory steps like planning, git commits, and status checks to verify completion.

How does git-based task tracking work with flowctl?

Git-based task tracking with flowctl captures status, evidence, and history for each task within a central local task store, ensuring deterministic orchestration and reducing state drift across the repository.

What is the best way to enforce mandatory guardrails when implementing a spec?

Enforce mandatory guardrails when implementing a spec by applying the phase-driven workflow, which requires plan, epic, task creation, and done state verification via git commits and evidence artifacts.

Do I need a central task store to coordinate feature delivery across multiple tasks?

A central local task store is required to coordinate feature delivery, acting as the repository-local .flow directory that orchestrates epic-to-task execution and tracks deterministic completion states.

Can I use this workflow automation without committing evidence artifacts to git?

Workflow automation requires committing evidence artifacts to git, as these artifacts alongside status checks are enforced as mandatory guardrails to verify task completion and prevent drift.

When do I need deterministic orchestration for software task execution?

Deterministic orchestration for software task execution is needed when delivering features from an epic across multiple tasks, ensuring consistent execution from planning to completion with strict traceability.