gsd-secure-phase

To retroactively verify threat mitigations, apply a secure-phase audit to the completed phase work. This validates existing mitigations against your documentation and updates SECURITY.md with confirmed results.

Yes, you can audit mitigations using a PLAN.md threat model. Apply the secure-phase workflow to artifact-based phases where PLAN.md exists to run verification from artifacts and ensure alignment.

A phase security audit retroactively verifies that threat mitigations are correctly implemented and documented for completed work. You need it when confirming finished phase work meets security requirements.

Yes, the secure-phase workflow preserves all predefined workflow gates during execution. It audits mitigations and updates security documentation without altering or bypassing established gates.

To update SECURITY.md with verified mitigations, execute the secure-phase workflow for the specified completed phase. The audit process automatically updates the file with verified mitigation status.

Retroactive threat mitigation verification requires a SECURITY.md file to audit mitigations, or a PLAN.md threat model for artifact-based phases. Without these existing documents, the secure-phase workflow cannot perform verification.