risk-and-scope-triage

Assess task risk and scope by evaluating the potential blast radius and identifying affected modules before planning. This process prevents unforeseen issues by determining if a change is isolated or requires decomposition into smaller tasks.

Check for upstream sync conflicts by analyzing modifications to shared upstream files versus private-fork-only files. This identifies potential merge issues early, helping you decide whether to proceed directly or use a feature branch.

Decompose a task based on scope evaluation when the blast radius indicates a complex modification affecting multiple modules. If the risk assessment reveals high impact across shared files, breaking the task down ensures efficient planning.

Risk triage works by identifying affected modules within specific directories like `apps/api/src/app/endpoints/ai/` and `libs/ui/src/lib/chat-widget/`. It evaluates changes in these paths to measure the overall scope accurately.

The best way to evaluate blast radius is to run a risk assessment as the first step of a new feature request. This determines the number of affected files and modules, guiding the decision to proceed or use a feature branch.

Use a feature branch instead of proceeding directly when risk assessment shows modifications to shared upstream files. This isolates potential blast radius impacts and prevents upstream-sync conflicts from affecting the main codebase.