gsd-secure-phase

Verify threat mitigations for completed security workflow phases and generate SECURITY.md reports.

Updated May 3, 2026
One-click install
npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-secure-phase-thiagovitale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-secure-phase
Source: https://github.com/ThiagoVitale/endless-crystal/tree/main/.codex/skills/gsd-secure-phase
Command: npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-secure-phase-thiagovitale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of retroactively verifying threat mitigations for a completed phase, saving time and ensuring security measures are in place.

Core Features & Use Cases

  • Retroactive Verification: Automatically checks and confirms that all necessary threat mitigations were implemented for a completed phase.
  • Phase-Based: Operates on a per-phase basis, allowing for targeted security audits.
  • Output Security: Generates an updated SECURITY.md file with the verification results.

Quick Start

Run the gsd-secure-phase skill to verify threat mitigations for the last completed phase.

Frequently Asked Questions about gsd-secure-phase

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

FAQPage Schema
How do I automate retroactive threat mitigation verification for completed project phases?

Retroactive threat mitigation verification is automated by running a phase-based security audit that checks completed phases against expected security artifacts and generates a verification report.

What is the best way to generate a SECURITY.md file from completed phase security audits?

Generating a SECURITY.md file from phase security audits involves scanning phase-specific documentation for implemented threat mitigations and outputting the verification results directly into the file.

Do I need phase-specific documentation to perform a phase-based security audit?

Yes, phase-specific documentation and existing security artifacts are required inputs to verify that all necessary threat mitigations were correctly implemented during the completed phase.

Can I verify threat mitigations for multiple completed phases at once?

No, threat mitigation verification operates on a per-phase basis, requiring targeted execution for each completed phase to accurately generate its respective security report.

Why does my retroactive security report show missing threat mitigations for a completed phase?

Retroactive security reports show missing threat mitigations when the phase-specific documentation lacks evidence of required security artifacts or when expected mitigation measures were not implemented.

When should I run a phase-based security audit for threat mitigation verification?

A phase-based security audit should be run immediately after a project phase is completed to retroactively verify that all defined threat mitigations were successfully implemented before moving forward.

Related Skills