01 · Plan
Describe what you need. Orwin asks only the questions that change what gets built, and writes the requirements, the solution design and the architecture as you answer, each section citing the answer it came from.
02 · Design
Before anything is built, Orwin reads the whole plan against itself. A rule written one way in the solution and another way in the architecture is a finding, with where it is and the fix.
03 · Build
The approved backlog becomes stories, each carrying its acceptance criteria and the decisions behind it. Your developers pick them up in their own tools, or Claude Code, Cursor and Codex read them over MCP.
04 · Test
Each rule you approved runs against the code as a test, written from the rule and not from the code. When one fails it says what happened, which rule it broke and where.
05 · Maintain
Every pull request is reviewed against the story it claims to implement, and an owner approves the merge. After it ships, Orwin keeps the plan true to the code.
Request early access to the pilot.
Works with the tools your team already uses