Cds secure phase
Skill Enakoneschniy/claude-dev-stack/vendor/cds-workflow/skills/cds-secure-phase
Retroactively verify threat mitigations for a completed phaseFrom its SKILL.md
npx -y skills add Enakoneschniy/claude-dev-stack --skill cds-secure-phaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.8 KB, 143 tokens by cl100k_base, as published. Nobody here has run it
<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>What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.