This is my personal software factory.
@michaelbfishbein · LinkedIn post · michaelbfishbein_thi… original · 2026-07-25
Post
This is my personal software factory.
It turns ideas into working products while I sleep. No babysitting coding agents with prompts all day.
Cursor and Claude Code made writing code way easier. The harder problem is building a system that can context engineer and manage itself.
My factory starts with a Skill called /factory. It’s the foreman that sends in the right worker for the job.
Factory runs this assembly line:
- The Interviewer
Reads the existing codebase (if there is one), extracts missing context from me via interview, and writes a product brief.
- The Planner
Turns the approved brief into small, testable features and development tasks.
- The Professor
Before anyone writes code, every task gets an exam. /factory-tests defines the success criteria for each task, and how the coding agent can prove to itself that what it built works or needs iteration.
- The Presenter
/factory-explain explains the plan to me like I’m 10, with visual metaphor and mermaid charts. Now that coding agents can write more code, faster than any human ever could, the new bottleneck is human understanding of the code. This skill solves that.
- CTO to SWE Handoff
/factory-handoff packages the brief, plan, tests, safety rails, and stop conditions into one work order. Factory uses the best models for the planning in the previous steps above, then hands the work order to a lower token usage model like Grok 4.5 for execution.
- The Coffee (Cursor or Claude Code /loop)
The night shift picks one task, builds it, takes its exam, records what happened, iterates if needed, then moves onto the next task. If it gets stuck, circuit breakers stop it from confidently digging a deeper hole while I sleep.
- The Grader
The student doesn’t grade it’s own homework. A fresh agent that never met the builder tries to break the result. /factory-review rereads the original plan, reruns tests, and finds anything that’s broken.
- Demo the Proof
Uses browser use and screen records itself performing the tests and adds an 11labs voiceover explaining what’s being proven. /auto-loom-proof sends me the narrated demo video showing evidence the software works.
- The Explainer
/factory-explain creates a simple owner’s manual explaining what got built. I understand my own codebase, so I can make decisions without becoming the bottleneck or outsourcing my thinking to AI.
NOTE ON BUILDING AI
Cursor and Claude Code have made writing code dramatically easier. But getting AI to work reliably and at scale for you can’t be fully automated.
LLM-as-judge helps, but a judge needs input from a subject matter expert. You still need a human reviewing the work and teaching the system how to perform better.