Robot Bakery
A Codex-orchestrated development platform that turns Jira tickets into a repeatable engineering workflow. All engineers use it; I continue to maintain and extend it.
Technical notes
My contribution
I developed Robot Bakery using Codex to orchestrate a standard software development lifecycle. Engineers start work with bakery process [jira ticket id]; the orchestrator drives the ticket through discovery, design, planning, implementation, testing, review, and closure.
A workflow with explicit gates
- Discovery
- Design
- PlanningHuman approval before implementation
- ImplementationTest-driven development
- TestingUnit, integration, and browser tests
- Review
- Closure
Each step pairs a task-tuned delegated agent with a read-only critic. The primary orchestrator uses codified scripts to enforce workflow state and sends work through further iterations until both agents agree on completion. Agent agreement does not replace human approval: operators approve plans before implementation and remain responsible for pull-request approval, merging, and deployment.
Pantry MCP: context that survives a session
I built Pantry, a local Model Context Protocol (MCP) service and CLI backed by SQLite. It preserves facts, decisions, procedures, and lessons across sessions, tickets, and repositories. Scoped, provenance-aware recall lets agents retrieve relevant context without loading the full history; its search uses local text similarity.
Pantry holds compact operational lessons. Repository-based knowledge files hold detailed, reviewable material about missteps and preferred patterns, shared across developers. Memory entries require accurate scope and provenance and exclude secrets.
