whiteboarding

Feature planning involves searching your codebase for existing patterns, researching technology options, and comparing approaches to produce an implementation-ready plan. This structured whiteboarding process ensures design decisions are grounded in your project's actual constraints before building starts.

Brainstorming technical designs works best when you map integration points and compare 2-3 approaches to identify trade-offs. This structured comparison ensures you evaluate different implementation paths systematically rather than guessing, yielding a concrete plan with clear checkpoints.

Codebase discovery for feature planning requires searching existing code to understand context, constraints, and current patterns. This ensures any proposed design integrates cleanly with your architecture and reuses established conventions instead of creating conflicting implementations.

Yes, feature planning supports implementation-ready handoff by breaking plans into concrete steps, files, and checkpoints. Plans saved to docs/plans/ can be directly executed using the /code-foundations:building workflow, ensuring a seamless transition from design to code.

Use structured whiteboarding for project planning when starting new features, designing complex solutions, or scoping large work. It is triggered by needs like mapping integration points, surfacing requirements, and evaluating technology options before committing to an implementation path.

Turning brainstormed ideas into an implementation plan requires structuring the output into concrete steps, files, and checkpoints. The final plan is saved to docs/plans/ to ensure the subsequent building phase has a clear, actionable roadmap to follow.