skills.rest
dobrinz123
dobrinz123COMMUNITY
Explore all skills by this author →
GitHub

gsd-secure-phase

Audit phase threat mitigations and update SECURITY.md with verified controls.

Updated Apr 9, 2026
Search Tags:#compliance#mitigation#security-audit#threat-model#threat#phase-management
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-secure-phase-dobrinz123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-secure-phase
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-secure-phase
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-secure-phase-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retroactively verify threat mitigations for a completed phase.

Core Features & Use Cases

  • Audit threat mitigations for completed phases to ensure security controls exist and are enforced.
  • Verify consistency between SECURITY.md and a threat model in PLAN.md, or provide guidance when a phase has not been executed.
  • Produce an updated SECURITY.md reflecting verified mitigations and recommended next steps.

Quick Start

Provide the target phase number to audit and verify its threat mitigations against available phase 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 audit threat mitigations for a completed development phase?▼

You can verify threat mitigations by providing the target phase number. The audit checks for a SECURITY.md file and cross-references it with the threat model documented in PLAN.md to ensure security controls are actively enforced.

What happens if my phase has not been executed yet but I want to check threat mitigations?▼

If the phase has not been executed, the audit provides specific guidance for updating SECURITY.md. It directs you on how to establish artifact-based verification and document the necessary security controls before execution begins.

Do I need a SECURITY.md file to verify phase threat models?▼

A SECURITY.md file is required to verify documented security controls. The audit checks for its existence and compares it against the threat model in PLAN.md, ultimately producing an updated SECURITY.md reflecting verified mitigations.

What is the best way to ensure consistency between my threat model and security documentation?▼

The best way to ensure consistency is to run an audit that verifies mitigations between SECURITY.md and the threat model in PLAN.md. This produces an updated SECURITY.md reflecting verified security controls and recommended next steps.

Can I use this audit for phases missing a documented threat model in PLAN.md?▼

If PLAN.md lacks a threat model, the audit focuses on the existence of SECURITY.md and provides guidance for unexecuted phases. It helps you establish artifact-based verification and update security documentation accordingly.

Related Skills

Explore More Software Engineering Skills→
diShine-digital-agencydiShine-digital-agency
1

shine-secure-phase

Audit threat mitigations and update SECURITY.md for completed phases.

Community
Advanced
GenproMMGenproMM

gsd-secure-phase

Verify threat mitigations for completed phases and update SECURITY.md.

Official
Intermediate
yusaduymazyusaduymaz

gsd-secure-phase

Verify implemented threat mitigations in completed GSD phase artifacts.

Community
Advanced
gesmith0606gesmith0606

gsd-secure-phase

Audit threat mitigations for completed phases and update SECURITY.md.

Community
Advanced