JRV

Portfolio / CASE STUDY

Private developer workflow

Solo Software Factory.

My factory playbook as an installable kit: a feature moves through specification, build, four reviews and an independent approver before it reaches a development branch.

MY ROLE

Independent workflow and tooling design

Why it exists

When one chat writes the code and also judges it, the review is weak. Branch names are also a poor guide to what deploys, so an automated merge can land closer to production than intended.

What I built

I built a kit that installs into an existing repository for Codex and Claude Code. One orchestrating chat runs seven separate agents: spec, builder, security, UX, UI and code reviewers, and an approver. Small Python helpers keep a local board, check report formats and handle the Git integration step. They never call a model.

Engineering decisions

01

Reject reports that do not match the work

Each report names its job, role, registered agent, attempt, base and head commit. The helper refuses stale or unregistered reports and a PASS that lists blocking findings. A job gets two review rounds in total, and anything unresolved after round two goes to a human.

02

Keep production out of reach

The kit will not create a feature branch until a development and production mapping is verified from evidence. It integrates only into a development branch, and only through a local Git transaction that checks both reviewed commits. Remote merges are blocked because no mechanism guards both.

03

Install without touching the host

The installer previews by default, refuses to overwrite a conflicting file, and adds the runtime directory to .gitignore first. The board is served read-only on loopback, with no approval buttons.

Capabilities in practice

  • Multi-agent workflow design
  • Review gates with auditable evidence
  • Safe Git automation
  • Cross-tool packaging for Codex and Claude Code

Status & scope

A private local repository, with no public URL. Its 19 tests use disposable Git repositories and fake agent reports. They do not show a live multi-agent run. Production promotion is deliberately left to a person. The design was inspired by zazencodes’ software-factory-claude-code.

Private repository solo-software-factory

KEEP EXPLORING

Specification Parser