planning

A technical implementation plan breaks down complex requirements into phased steps with clear acceptance criteria. Structure yours by analyzing the existing codebase, researching technical approaches, designing the solution with trade-offs documented, and organizing phases with risk and security considerations to guide development efficiently.

Solution design planning requires documenting multiple technical options with their trade-offs, phase breakdowns with deliverables, risk assessment and mitigation strategies, security considerations specific to your architecture, and acceptance criteria for validation. This ensures stakeholders understand the chosen approach and implementation path.

Evaluate technical approaches by documenting each option's trade-offs—performance, scalability, maintenance burden, dependencies—against your project constraints. Planning surfaces which approach aligns with YAGNI, KISS, and DRY principles while minimizing technical debt and security gaps.

Break requirements into phases with explicit tasks, dependencies, and acceptance criteria. Planning methodology guides codebase analysis to identify constraints, research to validate technical feasibility, and structured output that teams can execute incrementally with clear handoff points.

Yes, planning applies to system architecture by systematically analyzing component interactions, researching integration patterns, designing phase-gated rollouts, documenting trade-offs between monolithic and distributed approaches, and assessing operational and security implications at scale.