planning

To create a technical roadmap for complex features, you need structured plan creation with phased workflows and trade-off analysis. This involves documenting implementation phases, synthesizing research, and designing architectures to prevent scope creep and miscommunication across teams.

The best way to plan system architecture and manage dependencies is through structured planning that emphasizes YAGNI, KISS, and DRY principles. This approach generates self-contained plan directories with research, plans, and phase files for clear governance.

To document implementation phases and design guidance, you produce actionable plans with detailed phase files and research synthesis. This ensures risk, dependency, and timeline management are captured to align teams on the implementation strategy.

This planning approach generates documentation only and does not execute code. It outputs self-contained plan directories containing research, plans, and phase files to guide implementation strategy without modifying your codebase directly.

You need a phased workflow for feature planning and architecture design when working on complex technical work across large codebases and teams. It prevents scope creep and miscommunication by providing detailed phase documentation and trade-off analysis.