gsd-secure-phase

Audit security artifacts and generate an updated SECURITY.md with verified mitigations.

Updated Jan 28, 2025
One-click install
npx skills add https://github.com/aslaii/dotfiles --skill gsd-secure-phase-aslaii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-secure-phase
Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-secure-phase
Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-secure-phase-aslaii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Threat modeling and security controls are often incomplete or out of date after a project phase completes. This Skill audits existing threat mitigations by verifying the presence and accuracy of SECURITY.md and, when needed, uses PLAN.md with an attached threat model to guide remediation and documentation.

Core Features & Use Cases

  • Audits SECURITY.md to validate mitigations align with defined threat models and controls.
  • Falls back to PLAN.md with a threat model when SECURITY.md is not present, enabling artifact-driven mitigation updates.
  • Outputs an updated SECURITY.md that clearly documents mitigations and provides guidance for the next phase.

Quick Start

Run the gsd-secure-phase skill against a completed phase to generate an updated SECURITY.md with verified mitigations.

Frequently Asked Questions about gsd-secure-phase

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

FAQPage Schema
How do I audit threat mitigations for a completed project phase?

You can verify phase security by running this skill against existing artifacts to validate your SECURITY.md controls, or it falls back to PLAN.md threat models to generate an updated SECURITY.md with verified mitigations.

What is a SECURITY.md audit and when do I need it?

A SECURITY.md audit validates that your documented security controls align with defined threat models after a project phase completes, ensuring mitigations remain accurate and identifying remediation gaps for the next phase.

How do I update threat mitigations when SECURITY.md is missing?

When SECURITY.md is missing, this skill uses an attached threat model from your PLAN.md to guide artifact-driven mitigation updates, ultimately generating a new SECURITY.md with verified controls.

Can I audit security controls before a project phase has been executed?

Auditing security controls before phase execution supplies guidance rather than verifying completed mitigations, using your threat model to prepare an initial SECURITY.md for upcoming development work.

Do I need a threat model in PLAN.md to verify phase security?

A threat model in PLAN.md is required when SECURITY.md is not present for artifact-driven mitigation updates, but if SECURITY.md already exists, the skill audits it directly without needing the plan.

What are the limitations of auditing threat mitigations from project artifacts?

Artifact-based threat mitigation auditing relies on the presence and accuracy of existing SECURITY.md or PLAN.md files, meaning incomplete or outdated project documentation will limit the verification of security controls.