qualitylayer
maxritter · maxritter/qualitylayer
A workflow tool for coding agents that enforces visual planning, test-driven development, and independent code review.
Plan, build and review software with your coding agents. Work side by side in the App or browser, or use your favourite terminal or IDE.
Preview
What you can do with it
- Review clickable UI screens and diagrams before your agent starts coding
- Enforce a workflow where every code slice starts with a failing test
- Use an independent agent to verify that implementations match your original request
Safety check
Usable, but read the notes first.
- ●Installer downloads a remote script and pipes it to the shell.
install.sh - ●No clear license: check with the author before using it in a commercial product.
Automated scan of the repo files. Always review code you run.
From the README
QualityLayer
The software factory with you in the loop
Plan each change visually, then let your agents build and verify it. Work side by side in the App or browser, or use your favourite terminal or IDE.
Install • Features • Docs • Website • Changelog
Download the App for macOS, Windows or Linux. 7-day trial.
Why QualityLayer
“With QualityLayer, developing software with agents finally feels like doing real engineering again.”
An engineer who uses QualityLayer
QualityLayer keeps design decisions and verification visible while your agents work.
| You get | How it works |
|---|---|
| A design you can review | Comment on diagrams and clickable screens, then approve the Plan before code changes. |
| Small, tested changes | Your agent builds in slices, each starting with a failing test. |
| An independent check | Agents that did not write the code check it against your request. Anything they cannot verify stays open for your decision. |
| Code health checks | Local checks flag complex functions and deeply nested code for your agent to review. Ask for a wider check to find duplication. Code health. |
| Visible decisions and effort | Each step records its decisions and results in your repository, with time and estimated model cost shown in the App. |
Made for medium and large changes. Small requests keep a short Plan and one slice; ask for a ready prompt if you prefer your plain agent.
Getting Started
Prerequisites
- A coding agent: Claude Code, Codex, Pi or OpenCode, installed and signed in. Choose it in the App or browser. Other agents connect through the CLI.
- Your own subscription (Claude or ChatGPT plan, or API key). QualityLayer never charges for model usage.
- Git and a repository.
Installation
Download the App and open it. Setup activates your licence or starts the trial, installs the qualitylayer command and connects your agents. On a server, in WSL or in a container:
curl -fsSL https://qualitylayer.dev/install.sh | bash # macOS, Linux, WSL
irm https://qualitylayer.dev/install.ps1 | iex # Windows PowerShell
The App updates itself; without it, run qualitylayer update. Installation guide.
Uninstalling
qualitylayer uninstall undoes what the installer changed; your plans stay. On Windows, even when the App is gone:
& ([scriptblock]::Create((irm https://qualitylayer.dev/install.ps1))) -Uninstall
Coming from Pilot Shell 11
Run pilot update to install QualityLayer v12, or download it directly. Keep Pilot Shell 11 alongside it until you are ready to remove it; your paid licence works with both. Import memories per project when you are ready. Moving from Pilot Shell.
First Steps
In the App or browser, choose + New, pick your repository and agent, and describe the change:
Plan retries for failed webhooks and stop after a few tries.
- Answer your agent's questions and comment on the Plan beside its conversation.
- Approve the Plan and start the build. Your agent continues through Outline, Implement and Verify.
- Review the result and its evidence. Checks that need you, or could not run, stay open for your decision.
| Where you work | How to start |
|---|---|
| App or browser | Choose In QualityLayer to keep the agent beside the task. |
| Your terminal or IDE | Choose In my terminal, app or IDE to copy the request, or ask there: “Using QualityLayer, plan retries for failed webhooks.” |
| Another agent | Agents that run shell commands can use the CLI. Supported agents. |
To continue elsewhere, stop the active run, then ask: “Using QL, continue verification of task retry-webhooks.” Your Plan, changes and evidence stay with the task.
QualityLayer runs only when you ask for it. Your first task.
The Workflow
Each step writes a Markdown file in your repository. Read questions, decisions and results in the App. You approve the Plan and the finished change; QualityLayer pushes only with your approval and leaves merging to you.
| Step | What happens |
|---|---|
| Discuss | Settles what done means and clarifies a bug report |
| Research | Agents read how your code works today; a bug is reproduced and diagnosed here |
| Plan | Artifact, diagrams and checks, approved by you |
| Outline | The build session splits the approved Plan into small slices |
| Implement | Each slice starts with a failing test |
| Verify | Every point of your request, with its evidence |
| Review | A walkthrough of the change, approved by you |
| Pull request | Failing checks fixed; the task stays open until you merge |
Two levels
Engineering starts with a technical plan. Product starts with a brief that becomes a product requirements document. Choose at Setup or change it in Settings › Workflow or the task header. How they differ.
Artifacts
Ask your agent for a mockup, diagram or clickable artifact. Compare versions in the App, pin feedback and restore earlier versions. Keep the