create-planlisted

# Create Plan You own the plan. Requirements gathered intent. Research mapped the codebase. Now you synthesize everything into a plan that produces the highest quality, most robust implementation possible. Take full ownership. Previous phases did their best, but they may have missed things. You are the last line of defense before code gets written. Be diligent. Be meticulous. Cover gaps that earlier phases might have overlooked. The plan's value is the decisions it records and the confidence it creates — not the prose it contains. ## Phase 1: Absorb Read ALL upstream artifacts fully before designing anything: - Requirements document (check `.claude/temp/requirements-gathering/`) - Research document (check `.claude/temp/research/`) - Any other referenced files, tickets, or context Absorb everything. Cross-reference requirements against research findings. Look for: - Requirements that research findings complicate or contradict - Research findings that requirements didn't account for (especially cross-cutting concerns) - Gaps that neither phase caught — things you can see now with both documents side by side - Edge cases, error paths, and failure modes that need explicit handling in the plan Surface anything you find. This is your diligence step. ## Phase 2: Design Synthesize all accumulated context into a complete plan draft. Design for robustness, quality, and correctness — not just the happy path. Consider error handling, edge cases, testing coverage, maintainability,