Everything I built gets delegated. One thing doesn’t.
Eight years at the same studio, front-end developer to principal. These days most of what I build is the pipeline my team ships inside rather than the features that go through it.
What the machinery does
Open a tile for the specifics. That last one is the job.A skill library that guards its own index
Every skill states what it owns and what it refuses, with authoring rules for the next one. Two skills can’t claim the same job and answer differently on Tuesday.
Plan, then critique, then execute
An agent drafts the plan; a second pass argues with the draft before a line is written. Disagreement is cheapest while nothing exists yet.
Review that sizes its own depth
The diff is risk-assessed first. A copy change gets a skim; anything touching auth or deploys is read line by line, with a named human owner.
And then the handover, studio-wide
Out of one client team and into every project, plus the internal sessions where it gets taught. A pipeline one person understands is a single point of failure.
The decision to ship
This one doesn’t delegate. The risk call, the second reading and the decision to ship stay with a person — that’s the line the rest of it exists to protect.