implementation-approach

Implementation strategy selection depends on your project constraints and technical dependencies. Vertical slice approaches isolate feature stacks end-to-end; horizontal slice approaches layer by tier; hybrid combines both. Assess your codebase structure, team capacity, and risk tolerance to determine which fits best.

Risk assessment identifies and mitigates implementation hazards early. Map technical dependencies, verify constraints against your architecture, document potential failure points, and establish verification levels (L1-L3) to catch issues at each phase before they cascade into larger problems.

The strangler pattern replaces legacy functionality incrementally by routing new requests to replacement code while maintaining old systems in parallel. Use meta-cognitive analysis to identify replacement phases, define integration points clearly, and verify each phase meets functional and technical requirements before advancing.

Yes. Creative strategy combination tailors implementation approaches to your specific constraints. Analyze your existing codebase, technical stack, and project goals, then blend strategies—such as vertical slices for high-risk components and horizontal phases for stable layers—to optimize outcomes.

Document the rationale behind strategy selection, including constraint verification results, identified risks and mitigations, integration points, phase definitions, and reference patterns applied. This creates accountability and enables team alignment on why specific approaches were chosen over alternatives.