Plan Writing

This is for breaking down work into short, verifiable tasks without drowning in template bloat. The core idea is solid: keep plans under a page, make each task take 2-5 minutes, and always know how to verify you're done. It pushes you to be specific (not "add authentication" but "install next-auth, create the API route") and only include scripts that matter for your project type. Plans go in the project root with dynamic names, not hidden in docs folders. It's opinionated about staying minimal, which is refreshing when most planning frameworks encourage overthinking. Best for feature work, refactors, or complex bugs where you need structure without ceremony.