formax-rolling-plan-loop-workflow

Create rolling plan folders with README, TODO-INDEX, and a fixed implement-test-review-commit loop.

192|7|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/yusifeng/formax --skill formax-rolling-plan-loop-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: formax-rolling-plan-loop-workflow
Source: https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-rolling-plan-loop-workflow
Command: npx skills add https://github.com/yusifeng/formax --skill formax-rolling-plan-loop-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables teams to standardize project delivery by creating a reusable rolling plan loop directory with a README and a TODO-INDEX, making it easy to kick off and track repeated work.

Core Features & Use Cases

  • Rolling plan blueprint: Establishes a consistent folder structure under plans/<topic-slug>/ with documented goals and scope.
  • Fixed execution loop: Enforces a repeatable cycle: implement, targeted test, codex review, and commit for incremental progress.
  • Template-driven bootstrap: Provides reference templates in references/ to quickly bootstrap new plans and track unfinished work.

Quick Start

Follow the rolling-plan workflow to initialize and maintain a looping delivery process for your projects.

Frequently Asked Questions about formax-rolling-plan-loop-workflow

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

FAQPage Schema
How do I create a standardized rolling plan workflow for project delivery?

A rolling plan workflow standardizes project delivery by creating a directory structure under plans/<topic-slug>/ with a README.md and a TODO-INDEX.md. This setup establishes consistent goals, scope, and tracking for repeated work across similar tasks.

What is the implement, test, codex review, and commit loop pattern?

The loop pattern is a fixed execution cycle for incremental progress: implement, targeted test, codex review, and commit. It enforces a repeatable workflow structure that guides repetitive tasks through consistent development and review stages.

How do I bootstrap new plans and track unfinished work efficiently?

Bootstrap new plans using template-driven reference files in the references/ directory. These templates quickly initialize the plan structure and TODO-INDEX.md, allowing you to track unfinished work and maintain a rolling plan loop.

Can I use this rolling plan loop for repetitive task workflows without external dependencies?

Yes, the rolling plan loop requires no external dependencies. It uses a lightweight, template-driven setup with reference templates to bootstrap new plans, making it suitable for repetitive workflows without additional packages.

What's the best way to maintain a rolling plan directory structure for ongoing tasks?

Maintain a rolling plan directory structure by following the fixed workflow loop and updating the TODO-INDEX.md. This approach tracks unfinished work within the plans/<topic-slug>/ folder, ensuring reliable delivery across similar tasks.