Your first feature in 4 steps
After installing, here's how you ship your first feature with Codev OS.
We know Claude Code could probably one-shot a simple todo app. For simple things, this process may seem heavyweight — but as systems get more complex, the time invested up front on the spec and plan pays dividends.
In the Architect terminal, describe what you want to build. The AI will help you refine it into a structured spec with requirements, edge cases, and success criteria.
Let's spec out a new project: a simple HTML-based todo list manager that runs on the command line with CRUD operations.
After a few rounds of questions, the Architect will say the spec is ready. You can ask it to open the file so you can review it:
Can you use af open to show me the spec?
Reviewing the generated spec in Tower's file viewer
You can leave annotations on the spec — click any line to add a comment. Once you're done, tell the Architect to address your annotations and it will update the spec accordingly.
Click any line to leave inline comments on the spec
Once you're happy with the spec, tell the Architect to spawn a builder. It runs in an isolated git worktree — it can't mess with your working directory. You'll see the builder appear in the right panel of Tower, reading the spec and starting work.
Looks good. Spawn a builder to work on it.
Builder spawned — reading the spec and protocol in its own worktree
The builder's first move is a 3-way review of your spec — Gemini, Codex, and Claude all weigh in with findings and suggestions. The builder addresses the feedback, updates the spec, and moves on.
Gemini approves, Codex requests changes, Claude comments — the builder addresses all feedback
The builder opens the updated spec for your review. Read through it, and if you're happy, tell the Architect to approve:
The updated spec open in Tower's file viewer — review and approve
The builder writes a plan based on your spec. Note that the plan includes multiple phases in JSON — these phases will be enforced with reviews after each phase to catch bugs sooner. Review it and tell the Architect to approve.
The plan — phased implementation with testing strategy and success metrics
Approve the plan.
With a spec and an approved plan, the builder works autonomously for hours — not minutes. You can watch progress from the dashboard as it works through the phases.
Builder working through phase 1 of 3 — 50% complete, 16 minutes elapsed
When the builder is done, it sends a message to the Architect explaining it's completed the PR.
Builder notifies the Architect that the PR is ready for review
All done. No builders active. Your first project is complete.
PR merged, builder cleaned up — 65 tests passing, zero dependencies
This isn't just code that works.
What you get is the complete package: a spec that describes the feature, an implementation plan, a review with lessons learned, a comprehensive commit history, and a full suite of tests. For a toy todo app, this might seem like overkill — but as your codebase grows, these artifacts become essential for maintaining quality.
Want to see the output? Browse the repo, its history, and the tests:
github.com/cluesmith/todo-mgr
Codev OS 
