planning

A technical implementation plan breaks down feature requirements into scoped tasks, architectural decisions, and execution steps. Define requirements, analyze trade-offs between approaches, document system changes, and produce a roadmap with file-path references and estimated effort to guide development.

System architecture planning includes requirement analysis, design options with trade-off comparisons, scalability and security considerations, codebase impact assessment, and implementation sequencing. Document each component's role, dependencies, and integration points with reference to existing code patterns.

Trade-off analysis compares implementation options across dimensions like maintainability, scalability, security, and development effort. Present multiple solutions with concrete pros and cons for each, aligned to project constraints and established development rules.

Yes, the planning process applies across diverse projects. Requirement breakdown, architectural evaluation, and roadmap creation work independently of specific frameworks or languages, focusing on scope, design clarity, and implementability.

Requirement analysis defines feature boundaries, dependencies, and success criteria. Break down scope into discrete tasks, identify codebase integration points, flag blockers, and document assumptions to ensure complete and traceable implementation coverage.