Plan Writing

Breaks down features, refactors, and complex fixes into short, verifiable tasks with clear completion criteria. Each task should take 2-5 minutes and have a specific outcome you can check. Plans live in your project root as task-specific markdown files, not buried in docs folders. The key insight here is staying ruthlessly minimal: if your plan is longer than a page or has more than 10 tasks, you're overplanning. It pushes you to be concrete (not "add authentication" but "install next-auth, create the API route") and only include verification scripts that actually matter for what you're building. Good for when you need structure without drowning in process.