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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents overlooked or unverified security mitigations by helping you audit a completed phase and ensure the expected threat-model protections are actually documented and consistent.

Core Features & Use Cases

  • Mitigation audit with SECURITY.md: When SECURITY.md exists, it audits and verifies that mitigations match the phase’s expected threat considerations.
  • Fallback to planning artifacts: When SECURITY.md is missing but PLAN.md with a threat model exists, it runs verification based on the available artifacts.
  • Guardrail for incomplete execution: If the phase was not executed, it exits with guidance instead of producing misleading updates.

Quick Start

Run gsd-secure-phase for your desired phase number to produce an updated SECURITY.md based on existing security documentation or available threat-model planning 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 after completing a development phase?

Use a phase review to validate completed phase threat mitigations by checking SECURITY.md against expected threat considerations, or falling back to PLAN.md planning artifacts to generate an updated SECURITY.md.

What is documentation validation for security audits?

Security audit documentation validation retroactively confirms that threat mitigation documentation accurately reflects the protections planned and executed within a completed development phase.

Can I run a security phase review if SECURITY.md is missing?

Yes, a security phase review can execute using PLAN.md threat-model planning artifacts as a fallback when SECURITY.md is missing, outputting an updated security document derived from available repository artifacts.

What happens if I run mitigation verification on an unexecuted phase?

Running mitigation verification on an unexecuted phase triggers a safe exit with guidance instead of generating misleading SECURITY.md updates, preserving workflow gating to prevent inaccurate security validation.

When do I need to perform a phase review for incident prevention?

Perform a phase review for incident prevention immediately after a development phase finishes to ensure expected threat-model protections are accurately documented, consistent, and actively mitigating risks.