crew-flow

Automate plan, implementation, and review cycles for software changes.

8|1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill crew-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crew-flow
Source: https://github.com/JoeCP17/LLM-Dot-files/tree/main/codex/skills/crew-flow
Command: npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill crew-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you complete complex tasks by running a full Plan → Work → Review loop and iterating until issues are resolved or you choose to stop.

Core Features & Use Cases

  • End-to-end cycle orchestration: Creates a per-cycle state file and drives a full planning, implementation, and review sequence in one workflow.
  • Controlled iteration: Re-runs Work using Review findings when critical or high issues are detected, up to a configurable cycle limit.
  • Practical team-style cadence: Fits scenarios where you want Codex to not only implement, but also verify changes and respond to feedback.

Quick Start

Run the crew-flow skill for the task you want Codex to plan, implement, and review in one loop.

Frequently Asked Questions about crew-flow

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

FAQPage Schema
How do I automate an end-to-end plan, implement, and review cycle for repository changes?

To automate an end-to-end cycle, you orchestrate planning, implementation, and review phases in one workflow. This loops the implementation phase using review findings until critical issues are resolved or user-controlled cycle limits are met.

What is an iterative code review workflow for software implementation?

An iterative code review workflow is a process where implementation is automatically refined based on review findings. It loops the work phase using feedback when critical or high issues are detected, stopping only when issues are resolved or round limits are reached.

How do I set up workflow automation that loops implementation and code review steps?

To set up workflow automation that loops implementation and code review, you configure user-controlled round and cycle limits. The automation drives the sequence and stores the cycle state under a specific directory to track progress across iterations.

Can I control the iteration limits when automating plan, build, and review cycles?

Yes, you can control iteration limits by setting user-controlled round and cycle limits. This ensures the build and review loop stops automatically when limits are reached, or you can choose to stop the workflow manually at any point.

Where does automated workflow automation store cycle state for iterative code review?

Automated workflow automation stores cycle state under the .codex/crew/ directory. This ensures the iterative plan, work, and review loop maintains its progress and findings across each refinement cycle until stop conditions are met.