Cds Secure Phase

Name: Cds Secure Phase
Author: Enakoneschniy

ASecurity

Retroactively verify threat mitigations for a completed phase

5 stars
0 votes
0 copies
2 views
Added May 28, 2026

developmentbashsecurity

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add Enakoneschniy/claude-dev-stack --skill cds-secure-phase --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cds Secure Phase?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cds Secure Phase

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/enakoneschniy-cds-secure-phase/badge)](https://www.skillsdirectory.com/skills/enakoneschniy-cds-secure-phase)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: cds-secure-phase
description: "Retroactively verify threat mitigations for a completed phase"
argument-hint: "[phase number]"
allowed-tools:
  - Read
  - Write
  - Edit
  - Bash
  - Glob
  - Grep
  - Task
  - AskUserQuestion
---

<objective>
Verify threat mitigations for a completed phase. Three states:
- (A) SECURITY.md exists — audit and verify mitigations
- (B) No SECURITY.md, PLAN.md with threat model exists — run from artifacts
- (C) Phase not executed — exit with guidance

Output: updated SECURITY.md.
</objective>

<execution_context>
@$HOME/.claude/cds-workflow/workflows/secure-phase.md
</execution_context>

<context>
Phase: $ARGUMENTS — optional, defaults to last completed phase.
</context>

<process>
Execute @$HOME/.claude/cds-workflow/workflows/secure-phase.md.
Preserve all workflow gates.
</process>