skills.rest
GenproMM
GenproMMOFFICIAL
Explore all skills by this author →
GitHub

gsd-secure-phase

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

Updated Apr 3, 2026
Search Tags:#phase management#document update#security verification#project security#automated compliance
One-click install
npx skills add https://github.com/GenproMM/MMLab_TOOLS --skill gsd-secure-phase-genpromm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-secure-phase
Source: https://github.com/GenproMM/MMLab_TOOLS/tree/main/.claude/skills/gsd-secure-phase
Command: npx skills add https://github.com/GenproMM/MMLab_TOOLS --skill gsd-secure-phase-genpromm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Retroactive Verification: Automatically verify threat mitigations after a phase is completed.
  • Phase Execution States: Handles three states: (A) SECURITY.md exists, (B) No SECURITY.md but PLAN.md exists, (C) Phase not executed.
  • Output: Updates the SECURITY.md file with the verification results.
  • Use Case: After completing a phase in a project, use this Skill to automatically verify the implemented security measures and update the documentation accordingly.

Quick Start

Run the gsd-secure-phase skill with the phase number you want to verify, like: 'gsd-secure-phase 2'.

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?▼

To automate retroactive threat mitigation verification for completed project phases, use a tool that checks for SECURITY.md or PLAN.md existence and updates the security documentation based on the executed phase state.

What happens during security verification if a SECURITY.md file does not exist?▼

If SECURITY.md does not exist, security verification checks for the presence of PLAN.md to determine if the phase was executed. It then generates and outputs an updated SECURITY.md file based on the available project planning documentation.

Can I verify automated compliance for a phase that was not executed?▼

Automated compliance verification handles phases that were not executed by identifying the missing execution state. It processes this condition alongside existing SECURITY.md or PLAN.md files to output accurate security documentation updates.

What is the best way to update SECURITY.md after completing a project phase?▼

The best way to update SECURITY.md after completing a project phase is to run an automated verification skill with the specific phase number, which checks threat mitigations and outputs the updated security documentation directly.

Do I need a PLAN.md file to perform project security verification on completed phases?▼

You do not strictly need a PLAN.md file to perform project security verification, as the process handles three distinct states: existing SECURITY.md, missing SECURITY.md but existing PLAN.md, and phases that were not executed.

Related Skills

Explore More Software Engineering Skills→
dobrinz123dobrinz123

gsd-secure-phase

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

Community
Advanced
deerawandeerawan
1

gsd-secure-phase

Audit completed phase threat mitigations and update SECURITY.md.

Community
Intermediate
tinner-deinnotinner-deinno

gsd-secure-phase

Audit SECURITY.md or reconstruct threat mitigation verification from PLAN.md artifacts.

Community
Intermediate
ThiagoVitaleThiagoVitale

gsd-secure-phase

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

Community
Advanced