gsd-secure-phase

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

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-secure-phase-coco-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-secure-phase
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-secure-phase
Command: npx skills add https://github.com/coco-research/coco --skill gsd-secure-phase-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill retroactively verifies whether a completed phase has the expected threat mitigations, helping teams confirm security work was actually finished and documented.

Core Features & Use Cases

  • Phase-based security audit: Reviews a specific completed phase or the latest finished phase when no phase number is provided.
  • Artifact-aware verification: Works from an existing SECURITY.md, or reconstructs the review from PLAN.md and related phase artifacts when SECURITY.md is missing.
  • Controlled remediation output: Produces an updated SECURITY.md and preserves workflow gates so security validation stays consistent.
  • Use case: A team finishes an implementation phase and wants to confirm every planned mitigation was addressed before moving forward.

Quick Start

Ask the skill to verify the latest completed phase and update SECURITY.md with any missing threat mitigation checks.

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 for a completed development phase?

To verify threat mitigations, audit the completed phase against existing security artifacts. The skill checks if planned mitigations were addressed and updates SECURITY.md with the audit results, preserving workflow gates.

Can I audit phase security if my project only has a PLAN.md?

Yes, you can audit phase security with only a PLAN.md. The skill reconstructs the threat model review from PLAN.md artifacts when SECURITY.md is missing, producing an updated security record from available evidence.

What happens to workflow gates when updating SECURITY.md after a phase audit?

Workflow gates are strictly preserved when updating SECURITY.md. The skill produces controlled remediation output that maintains existing security validation checkpoints while adding the latest audit results.

How do I retroactively check security work for phases that were never executed?

Retroactive security checks for unexecuted phases are supported. The skill audits phases that were never executed by reconstructing the expected threat mitigations from available evidence and generating a SECURITY.md.

Does the phase security audit work automatically on the latest finished phase?

Yes, the phase security audit works automatically on the latest finished phase. When no specific phase number is provided, the skill defaults to reviewing the most recently completed implementation phase for threat mitigation.

Why update SECURITY.md instead of creating a new file after a threat mitigation audit?

Updating SECURITY.md maintains a continuous security record rather than fragmenting documentation. This controlled remediation output preserves workflow gates and consolidates phase audit evidence into a single source of truth.