secure-phase

Retroactively verify threat mitigations for a completed phase

SKILL.md

GitHub
<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: $ARGUMENTS — optional, defaults to last completed phase. </context> <process> Execute @${CLAUDE_PLUGIN_ROOT}/workflows/secure-phase.md. Preserve all workflow gates. </process>

Related in other

limits-colimits

Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context polluti...

by parcadei
3,392

ddttom-allaboutv2-claude-skills-block-collection-and-party

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration p...

by mattnigh
20

nodnarbnitram-claude-code-extensions-claude-skills-esphome-confi

This skill should be used when the user asks to "create an esphome config", "set up an esp32 device", "configure esphome...

by mattnigh
20