This is a deliberately provocative title, so let me be clear about what I mean: I run a solo developer consulting practice. I used to subcontract some work — design review, QA, documentation. I no longer do.
The plugin that changed this is a custom Claude Code skill I built for my workflow. Let me walk through what it actually does.
What I Was Paying Others For
Before I get to the plugin, the context: as a solo developer, I was regularly subcontracting three things:
- Design review — Someone to look at my UI implementations and catch the obvious design problems I'm blind to
- QA passes — Someone to actually use the feature and try to break it
- Documentation — Someone to write user-facing docs from my internal notes
Each of these is not a full-time job. But each required a human with specific skills and context about the project. That meant onboarding, async coordination, and the overhead of managing contractors.
The Plugin
The skill I built, /quality-pass, runs a structured review sequence:
# quality-pass command
You are doing a quality pass on a recently completed feature.
Run the following checks in sequence:
## 1. Design Review
Look at the component files changed in the last commit.
For each UI component:
- Check spacing consistency (use our 8px grid)
- Check that interactive elements have hover/focus states
- Check that error states are handled and displayed
- Check color usage against our design tokens in globals.css
## 2. Functional Review
Read the code and identify:
- Edge cases that aren't handled
- Error conditions that aren't caught
- Input validation that's missing
- Happy path vs. unhappy path coverage
## 3. Documentation
Generate user-facing documentation for the feature:
- What it does (one sentence)
- How to use it (numbered steps)
- Any limitations or gotchas
Output each section clearly separated.
When I finish implementing a feature, I run /quality-pass and get back a structured report covering all three areas. I review the report, fix what needs fixing, and ship.
What It Actually Catches
The honest take on quality: it catches the real issues I would have caught in a design review about 70% of the time. Missed focus states, inconsistent spacing, unhandled error conditions — it finds these reliably.
It catches maybe 50% of what a dedicated QA pass would catch. It won't catch interaction bugs that require actually using the feature, timing issues, or anything that emerges from real user behavior. But it catches the static analysis problems — missing validation, unhandled edge cases visible in the code.
Documentation quality is high — often better than what I'd write myself, because I'd write terse notes while the plugin writes clear user instructions.
What It Doesn't Replace
The plugin does not replace:
- A designer's judgment about whether the UX actually makes sense
- Real user testing for anything complex
- A technical reviewer for architecture decisions
- Anyone who catches bugs by actually using the software
Those are still real needs. For my specific consulting work — custom internal tools for small teams — the bar is lower. "Works correctly and looks professional" is usually sufficient. For consumer products with more demanding users, you'd need more.
The Solo Developer Thesis
The interesting implication: the economic model for solo developers has changed. A developer with good AI tooling can handle a broader surface area of work than was possible a few years ago.
The tasks that required collaboration aren't collaboration because they required multiple brains — they required multiple perspectives and skill sets. AI augments individual perspective.
This doesn't mean you never need other people. It means the threshold for when you need them is higher. For a solo developer, "need to ship this reliably" used to mean "need to hire help." Now, for a large category of projects, it means "run the quality-pass plugin and review the output."
That's a real change in the economics of software development, even if it sounds unglamorous.