Use when defining plans, specs, or task breakdowns for web application work that may be missing security requirements
Use when a repository wants stage-aware cybersecurity guidance during planning, risky implementation changes across authentication, authorization, tokens, secrets, middleware, outbound requests, file handling, CI, deployment, and other trust boundaries, post-implementation review, or pre-release hardening; do not trigger for doc-only, naming-only, formatting-only, or UI-only changes that do not affect a trust boundary
Use when implementation is complete or review is requested and the user may want a focused security review of the changed code
Use when a feature or project is nearing handoff or release and the user may want a stack-aware security check plan without automatic setup
Use when a session needs quick orientation to SentinelXPrime stages, checkpoints, guardrails, and the right SentinelXPrime skill to invoke