qsd-secure-phase

Audit SECURITY.md and validate threat mitigations for a completed phase.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/thecomputer07/qsd --skill qsd-secure-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qsd-secure-phase
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-secure-phase
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-secure-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify threat mitigations for a completed phase by auditing security artifacts and validating mitigations to ensure risk is reduced and compliance is maintained.

Core Features & Use Cases

  • Audits existing SECURITY.md when present to verify mitigations are complete and accurate.
  • Runs from artifacts when no SECURITY.md exists but PLAN.md with a threat model is available.
  • Provides guidance for unexecuted phases to establish baseline threat models and mitigations.

Quick Start

Run the secure-phase workflow on the target phase to verify mitigations.

Frequently Asked Questions about qsd-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 project phase?

To verify threat mitigations for a completed phase, you can audit existing security artifacts by running a secure-phase workflow that reads and updates SECURITY.md to validate mitigations are complete.

Can I audit security mitigations if a SECURITY.md file is missing?

Yes, you can audit security mitigations without a SECURITY.md file if a PLAN.md containing a threat model exists, allowing the workflow to run from phase artifacts and generate the security audit.

How do I establish a baseline threat model for an unexecuted project phase?

To establish a baseline threat model for an unexecuted phase, run the secure-phase workflow to provide guidance on necessary security mitigations before execution begins.

What is the best way to automate a security audit for phase artifacts?

Automating a security audit for phase artifacts involves executing a dedicated secure-phase workflow that validates mitigations and updates the SECURITY.md file while preserving all workflow gates.

Does the threat mitigation audit preserve existing workflow gates?

Yes, the threat mitigation audit preserves all workflow gates defined in the secure-phase workflow, ensuring compliance and risk reduction checks remain enforced during security validation.

Why do I need a PLAN.md with a threat model to run security audits from artifacts?

A PLAN.md with a threat model is required to run security audits from artifacts when SECURITY.md is absent, providing the necessary baseline threat data to verify mitigations for the completed phase.