risk-assessment-before-destructive-changes

To document a risk assessment before destructive shell commands, log the exact command, target paths, blast radius, checkpoint path, and rollback steps in the active task plan file.

The best way to prevent data loss during git reset hard or rm rf operations is to record a formal risk assessment capturing the blast radius and rollback steps in your task plan before execution.

To create a rollback plan for destructive file rewrites and chmod operations, define a writable checkpoint path and document the exact rollback steps in planning/active/<task-id>/task_plan.md.

You need to record a formal risk assessment for destructive changes whenever executing operations like rm -rf, git clean, git reset --hard, chmod, or broad file rewrites to ensure a durable decision log.

Executing destructive changes requires updating the planning/active/<task-id>/task_plan.md file format to log the exact command, target, blast radius, checkpoint, and rollback steps.

To enable safe rollback after destructive operations, record the exact command, target paths, blast radius, writable checkpoint path, and rollback steps in your active task plan.