It might seem like SpecDevShip's distinct roles — Product Manager, Designer, Art Director — are built for teams, and irrelevant when you're a solo indie developer doing all three jobs yourself. In practice, the separation is arguably more useful solo, not less, because nothing else is forcing you to context-switch between these modes deliberately.
Why wearing every hat doesn't mean skipping the hats
When you're both the person defining what your game is and the person building it, it's dangerously easy to let "what is this game actually about" quietly get decided implicitly, feature by feature, rather than deliberately. Running product-design's structured dialogue with yourself — even solo, even without another human on the other side of it — forces the "what and why" questions to get answered explicitly, in writing, instead of accreting as an unspoken set of assumptions you never actually checked against each other.
Art and design direction as a real creative checkpoint, even for an audience of one
The "pitch a few directions, pick one, then commit" model isn't just useful for managing a client or a team — it's useful for managing your own indecision. Indie developers are notorious for endlessly relitigating art style or UI direction mid-project because nothing ever forced a real, committed choice. Running art-direction/design-direction properly — actually generating distinct options and actually picking one, rather than vibing toward an ever-shifting style — is a forcing function against exactly that failure mode.
Light tier as the honest default for solo scope
Nearly everything in a solo project is light tier, and that's exactly right — you don't need a four-document pipeline to add a new enemy type. Reserve full tier for the handful of things that are genuinely architectural: your save system, your core progression/economy model, a networking layer if you add multiplayer later. Getting this distinction right solo matters because you don't have a team's slack to absorb an under-specified architectural decision made in five minutes because it felt like "just adding a feature."
Investigation discipline when you're the only debugger you've got
With no one else to bounce a bug against, the temptation to guess-and-check is strongest exactly when it's most expensive — you have no second pair of eyes to catch a wrong fix. The Investigate skill's insistence on a cited, verified cause is what a solo teammate would insist on if you had one.
Solo doesn't mean unstructured. It means you're the only person who'll notice if you skip the structure — which is exactly why it's worth keeping anyway.