Spec Driven Workflow

This enforces a two-phase workflow where Claude first writes a detailed specification, gets your approval, then implements it. It's built for cases where you want to review the plan before any code gets written, which honestly makes sense for anything non-trivial or when you're working in an unfamiliar codebase. The skill blocks Claude from jumping straight to implementation, forcing that spec review step. Trade-off is obvious: it adds friction and back-and-forth, so you probably don't want this for quick fixes or exploratory work. Best for features where the upfront thinking saves you from rewrites later.