gsd:secure-phase
Retroactively verify threat mitigations for a completed phase
npx skills add davepoon/buildwithclaude --skill secure-phase --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<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> @${CLAUDE_PLUGIN_ROOT}/workflows/secure-phase.md </execution_context> <context> Phase
What does the gsd:secure-phase skill do?
Retroactively verify threat mitigations for a completed phase
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill secure-phase --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.