risk-scan

To identify potential task impact and historical incidents, run a pre-check risk scan that enumerates affected files and correlates past incident logs to produce an actionable risk brief for safe planning.

A pre-task risk brief is a concise summary of potential impact, applicable quality rules, and past incidents. You need it during planning for tasks touching multiple files or modules to ensure safe L2 handoffs.

You can load quality criteria and affected file lists by executing a risk scan, which automatically fetches global quality rules, per-skill guidelines, and enumerates impacted modules to guide your planning.

Yes, you can use a risk scan to prevent repeating past incidents. It correlates historical incident logs with your current task's scope to align planning with previous decisions and avoid known mistakes.

Yes, the risk-scan pre-check works specifically for tasks touching multiple files or modules. It reads global quality rules and past incident logs to compile an actionable risk summary suitable for project teams.

When generating a risk brief for downstream handoffs, expect the output to be an L1 summary requiring an L2 review stage. It focuses on impact, quality rules, and incidents rather than executing the actual code changes.