think

To turn a rough idea into an approved build plan, you process the concept into a decision-complete implementation plan with explicit constraints, risk validation, and concrete execution steps. This ensures all architectural tradeoffs are finalized before any coding begins.

Documenting architecture tradeoffs requires selecting a direction, defining success criteria, and outlining value judgments within your repo context. This produces an approval-ready plan clarifying what to build, defer, and what evidence still matters before development.

To triage mixed project requests, you sort the incoming items into distinct categories: bugs, accepted improvements, cosmetic feedback, and out-of-scope items. This multi-item triage ensures clear decision-making and scope management before execution handoff.

Yes, you need current repo context to make accurate value and scope judgments. Deciding whether to keep, remove, or pivot a feature requires explicit constraints and risk validation based on the existing codebase to produce a viable execution plan.

An execution handoff plan must include concrete execution steps, identified risks, testing requirements, rollback notes, and follow-up actions. This transforms architecture choices and feature designs into a clear, actionable roadmap for the coding phase.

You should avoid a decision-complete planning approach for trivial changes that require no architectural choices or risk validation. It is designed for feature design, value judgments, and multi-item triage that explicitly need formal approval before coding.