Turn approved requirements into an implementation plan with tasks and a test plan. Use when planning a substantial feature from approved requirements before any implementation begins. Skip for small local changes (implement directly with focused tests), security reviews, and convention checks.
Review a change for security risks before it is accepted. Use when a change touches a trust boundary — file writes, paths, dependencies, stored secrets, network calls, telemetry, MCP, auth — and needs a decision before merging. Skip for feature planning, test writing, and convention checks.
Check a change against the repository's naming conventions and canonical vocabulary instead of reinventing patterns. Use when reviewing a finished change, or before finishing one, to verify it reuses what CONVENTIONS.md names. Skip for planning work, security reviews, and writing new tests.
Durable memory under docs/ is the source of truth over chat history; repository rules override model preference. If an instruction conflicts with repository memory, stop and report it.