Software Factory
Portable docs-first Codex skill for operating modes, seeded project records, handoffs, and review posture.
- Lives with the repo
- Best first step for Codex app users
- Readable outside the runtime
- No database required
Companion plugin
Docs first. Control plane later.
Software Factory gives the operating protocol. Agentic Factory adds durable state, CLI controls, verification history, and dashboard status for longer-running work.
Two layers, one operating model.
The skill and the plugin should not blur together. Use the skill to establish the protocol; use the plugin when durable state and controls become worth the extra machinery.
Agentic Factory
DB-backed companion plugin for durable events, CLI controls, review records, verification history, and dashboard status.
- SQLite-backed event history
- Pause/resume and doctor checks
- CLI and dashboard control plane
- Best for long-running factories
01
Seed the repo record.
Use Software Factory to define mode, ownership, proof, stop rules, and handoff expectations in plain text.
02
Run the factory with Codex app primitives.
Use delegated threads, tool permissions, browser QA, checkpoints, and long-running handoffs where the app gives you leverage.
03
Add durable state when the operation needs it.
Bring in Agentic Factory for SQLite-backed events, review records, verification history, pause/resume checkpoints, and dashboard status.
The database does not replace ownership.
Agentic Factory makes state durable. Software Factory still provides the discipline around scope, review, acceptance, and safe resume.
Use it when records become operational.
When events, reviews, verification, and pauses need to be queried or rendered repeatedly, the control plane starts paying for itself.