I built my personal site in one day with SpecDevShip. Here's the paper trail.
I built coreystruzan.com in one day of work and didn't fix a single line by hand. Here are the specs, task lists and agent conversations that show how it went.
Stop Vibe-Coding: Why Solo Developers Need a Spec-Driven Skill Pack for Their AI Coding Agent
Your AI coding agent can write anything you describe — which is exactly the problem. Here's how a 19-skill, spec-driven workflow keeps AI-assisted development from turning into chaos.
EdTech: Building Tools That Outlive the Person Who Built Them
Educational tools tend to live for years with minimal engineering attention — which makes documentation the thing standing between "still working" and "nobody knows why this broke."
Solo Indie Game Devs: Playing Product, Design, and Art All at Once
When you're the programmer, designer, and art director simultaneously, the workflow's role separation still helps — even with an audience of one.
Legacy Modernization: Rebuilding With Confidence Using Analysis-First
The hardest part of modernizing an old system usually isn't the new code — it's confidently knowing what the old system actually does.
Browser Extensions and Small Utilities: When Light Tier Is All You Need
Not every project needs the workflow's heavier gears — here's what a small, focused tool actually gets from SpecDevShip.
Data & ML Engineering: Investigating Pipeline and Model Bugs Systematically
"The model's just being weird" is the ML equivalent of "probably a race condition" — and just as unacceptable as a diagnosis.
API and Developer-Platform Teams: Specs as the Source of Truth
When your product is a contract other developers build against, the requirements document isn't internal process — it's the closest thing you have to the real product.
Internal Tools Teams: Light Tier as the Default at Enterprise Scale
Internal tooling gets starved of process at most companies — not because it doesn't matter, but because the standard process is too heavy to justify. Light tier changes that math.
Open Source Maintainers: Onboarding Contributors With a Real Spec Trail
"Why was it built this way" is the question every new contributor asks and every maintainer gets tired of answering from memory.
Agencies: Managing Multiple Client Codebases Without Losing Context
Context-switching between five client codebases in a week is where undocumented decisions cost the most — here's why.
Healthtech: Why Documentation Discipline Isn't Optional
When the cost of an undiagnosed bug or an unreviewed change is measured in patient-facing risk, "we'll document it later" stops being a reasonable plan.
Fintech and the Case for Approval Gates You Can Actually Audit
In a regulated space, "we reviewed it" needs to mean something specific and checkable. Here's how draft/approved status doubles as an audit trail.
Spec-Driven Workflows for Game Development Studios
Games blend engineering risk with genuine creative direction in a way most software doesn't — here's how the workflow's two collaboration models both come into play.
E-Commerce Teams: Keeping a Growing Storefront Codebase Sane
Checkout, inventory, and promotions logic accumulate special cases fast. Here's where spec-driven discipline earns its keep in a storefront.
Using SpecDevShip for Mobile App Development
App-store review cycles change the cost of getting something wrong. Here's how the workflow's discipline maps onto mobile's specific constraints.
Spec-Driven Development for SaaS Founders Building Their MVP
Speed to MVP and a workflow you won't have to retrofit later aren't actually in tension — here's how the tier system keeps them from colliding.
Release Automation: How SpecDevShip Derives Your Version Bump From Commit History
No more guessing whether a change is a patch, a minor, or a major — the answer was already written in your commit messages.
From Approved Tasks to Shipped Code: A Look Inside Implement-Tasks
What actually happens between a spec you signed off on and code landing in your repo — and why it commits the way it does.
Spec-Sync: Keeping Four Documents From Quietly Drifting Apart
Full-tier work produces four linked documents. Here's what happens when one of them changes after the others were already written.
How Design Direction and Art Direction Give Your Agent Real Creative Autonomy
One checkpoint, then full authority — the opposite collaboration model from everywhere else in the workflow, and just as deliberate.
Product Design vs. Product Analysis: Origination vs. Extraction
Two skills produce the same document — product.md — from opposite directions: one through dialogue, one through evidence.
The One-Folder-One-Topic Rule, and Why It Matters More Than It Sounds
A small naming discipline that keeps a growing codebase's spec history from turning into a junk drawer six months in.
Why Approval Gates Are the Feature You'll Underrate at First
Draft and approved sound like bureaucracy until the first time an agent tries to quietly revise a decision you thought was settled.
Design-First vs. Requirements-First: Choosing Your Starting Point
Full-tier work splits into two paths depending on one question: does something real already exist? Here's how to tell which one you're on.
Inside the Investigate Skill: How Root-Cause Diagnosis Actually Works
"Probably a race condition" is a shrug with technical vocabulary. Here's the actual three-step process SpecDevShip runs before any fix gets proposed.
The Tier Decision Explained: When Light Tier Isn't Enough
Most work is light tier. Here's exactly how the workflow decides when a change has actually crossed into full-tier territory — and why getting this call wrong in either direction costs you.