planning

Technical implementation planning breaks down feature requirements into phased milestones, architecture decisions, and acceptance criteria. Structure your plan across 3-6 phases: setup, architecture, implementation, and validation. Document dependencies, risk assessments, and quality standards to ensure scalability and security before development begins.

An architecture plan grounds design decisions in codebase analysis and research, addressing functional requirements, performance considerations, security constraints, and maintainability trade-offs. Include milestone sequencing, dependency mapping, risk identification, and acceptance criteria that enforce quality standards without delivering code.

Roadmap planning requires analyzing requirements, assessing technical trade-offs between scalability and complexity, identifying security and performance risks, and documenting mitigation strategies. Comprehensive planning produces actionable artifacts with clear milestones, dependencies, and acceptance criteria tied to both functional and non-functional goals.

Yes. Planning applies to codebase understanding and architecture redesign by analyzing current structure, identifying scalability gaps, documenting refactoring phases, and creating acceptance criteria for maintainability improvements. This produces detailed implementation plans that guide modernization without requiring code delivery upfront.

Planning prevents costly rework by researching requirements, analyzing architecture trade-offs, and documenting security and performance considerations before implementation. Comprehensive plans enforce quality standards and identify risks early, reducing scope creep and ensuring solutions remain scalable and maintainable.

Integrate security and performance analysis into each planning phase by identifying threats, compliance requirements, bottleneck risks, and optimization strategies. Document these considerations explicitly in milestones and acceptance criteria so implementation enforces standards without deferring critical decisions to development.