Verified:GitHub

gsd-secure-phase

Validate phase threat mitigations and update SECURITY.md from PLAN.md artifacts.

Updated Aug 23, 2026

Search Tags:#compliance #security audit #threat model #mitigation verification #workflow gating #project phase #secure documentation

Ready to run

npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-secure-phase-beibei-clic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-secure-phase
Source: https://github.com/BeiBei-Clic/ai-skills/tree/main/gsd-secure-phase
Command: npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-secure-phase-beibei-clic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Completed work often misses security verification, so mitigations stay unvalidated until problems appear later.

Core Features & Use Cases

Threat mitigation audit for a finished phase: Confirms that the phase’s security measures were applied and recorded in SECURITY.md.
Artifact-driven verification when SECURITY.md is missing: Uses existing PLAN.md threat-model artifacts to reconstruct and update SECURITY.md.
Safety guardrails for non-executed phases: Stops early when the phase was not actually executed and gives guidance instead of producing misleading results.

Quick Start

Ask an AI to run gsd-secure-phase for phase 3 to update SECURITY.md based on the phase’s plan and execution artifacts.

Frequently Asked Questions about gsd-secure-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify threat mitigations for a completed project phase?▼

To verify threat mitigations for a completed project phase, you can retrospectively validate applied security measures against existing artifacts. This process updates your SECURITY.md to confirm that planned protections were actually executed and recorded.

What is the best way to update SECURITY.md when it is missing?▼

Updating a missing SECURITY.md is possible by extracting threat-model artifacts from an existing PLAN.md. This reconstructs the required security documentation retrospectively to validate completed phase mitigations.

Can I run a security audit on a project phase that was not actually executed?▼

Running a security audit on a non-executed project phase triggers an early exit with guidance instead of producing misleading results. This safety guardrail prevents validating mitigations for work that was never completed.

Does retrospective security verification preserve existing workflow gating?▼

Yes, retrospective security verification preserves existing workflow gating and phase exits while updating your security documentation. It ensures that retroactively hardening a completed project phase does not disrupt your established compliance checks.

How to reconstruct security documentation using PLAN.md threat models?▼

To reconstruct security documentation using PLAN.md threat models, the system reads existing plan artifacts to identify planned mitigations. It then validates these against execution artifacts to produce an updated SECURITY.md.