Plan

Turns abstract feature requests into verified task lists that actually survive implementation. Built from 200+ real planning sessions, it enforces one simple rule: every task needs a concrete verification method, whether that's a passing test, a typecheck, or a curl command. The phases walk you through scoping (skip planning for tiny changes), exploration (read the actual code), decomposition (2-5 minute tasks with explicit dependencies), and tracking in Sibyl so plans outlive your context window. The parallelization markers are clever for orchestration handoff. Honest about replanning being normal, not failure. If you've ever written a plan that collapsed the moment you touched code, this codifies what makes the difference.