shine-secure-phase

Phase security verification confirms that threat mitigations are correctly applied and documented after a development phase. It audits SECURITY.md or validates threat models from PLAN.md artifacts to ensure required security controls are properly implemented.

Yes, if the phase has not been executed, the verification workflow provides guided remediation and security guidance. It uses your existing PLAN.md threat model to outline the required security controls before execution begins.

You can validate a threat model from PLAN.md by running the phase verification workflow. It cross-references your planned threat model with existing artifacts to confirm whether the required security controls have been properly applied and documented.

Yes, phase security verification explicitly preserves all existing workflow gates during the audit. It only updates SECURITY.md with confirmed mitigations, ensuring your established compliance and security documentation workflows remain fully intact.

No, a specific phase number is not strictly required because the workflow accepts an optional phase number argument. However, providing the phase number allows the audit to accurately target and verify the exact security controls for that specific development phase.