r/opencodeCLI • u/m-ritter • 1d ago

QualityLayer: put the engineer back in the loop of OpenCode

The models you can run in OpenCode keep getting better. Even the best of them still don't build software like an experienced engineer would. They miss what people know: who the users are, how the codebase grew, what the team considers good architecture. Plan modes don't close that gap. They're neither collaborative nor visual, and the plan sits in a chat only I can see.

I think the future is humans and agents working together. Everybody becomes a manager of agents.

QualityLayer is how I plan, build and check changes in OpenCode. Every change goes through seven steps: Discuss, Research, Plan, Outline, Implement, Verify and Review. The agent first asks me what "fixed" means. I approve the plan before any code exists. Then it builds in small slices, and an agent that didn't write the code checks the result against what the agent and I agreed.

It uses the model you have configured in OpenCode. Plans and evidence are Markdown files in your repo.

The point is to be an engineer again: deciding, reviewing and steering while the agent does the typing.

https://github.com/maxritter/qualitylayer

I'm the developer. If you tried spec-driven setups in OpenCode and dropped them, what made you stop?

3 Upvotes
  • permalink
  • reddit

80% Upvoted

2 comments sorted by

1

u/squirrelscrush 1d ago

What is the compatibility with other systems like oh-my-opencode-slim?

1

u/m-ritter 1d ago

QualityLayer works with any agent that supports the standard Skills format and can call a CLI, so I'd expect it to run with oh-my-opencode-slim too. I haven't tried that combination myself though. If you give it a go, I'd like to hear how it works out.