Use when executing a written implementation plan with verification at every step. Checkpoint-based recovery, drift detection, three-stage review, circuit breakers, and execution fidelity scoring. Every completion claim requires fresh evidence. Triggers: "execute plan", "run this plan", "implement this plan".
Auto-loaded at session start. Resumes active pipelines, routes tasks to stn-skills. Triggers: session start, /stn-skills:session-init.
Use before any feature design, approach exploration, or architectural decision. Required before plan-writing. Dispatches parallel subagents for multi-lens analysis, weighted scoring, and adversarial stress-testing. Produces validated design specs. CHAINS TO plan-writing on completion — MUST invoke via Skill tool. Triggers: "brainstorm", "design", "explore approaches", "how should we build".
Use when a design spec or requirements need decomposition into executable tasks, before writing any code. DAG-based task decomposition with zero placeholders, complete code in every step, adversarial verification, and rollback planning. CHAINS TO plan-execution on completion — MUST invoke via Skill tool. Triggers: "write a plan", "plan this", "break this down".
Use when auditing a repository for production readiness, security, or code health. Dispatches up to 13 specialized auditor subagents in parallel with file:line evidence for every finding. Technology-agnostic, works with any language and framework. Triggers: "audit", "review the repo", "code health", "security scan".
Use for end-to-end feature delivery from idea to verified code. Orchestrates brainstorming, plan-writing, and plan-execution with validated handoffs and 11 gates. No shortcuts, no skipped gates, no unverified claims. Triggers: "build feature", "build this", "implement end-to-end", "full pipeline".
Use when setting up or updating project quality standards. Generates tech-stack-specific CLAUDE.md and hooks aligned with all 13 audit domains. Preventive counterpart to codebase-audit — bootstrapped projects produce zero audit findings. Triggers: "bootstrap", "set up standards", "generate CLAUDE.md".
Use between pipeline phases to validate handoff artifacts against contracts. Catches incomplete specs, ambiguous criteria, and plan defects before they propagate downstream. Invoked automatically by build-feature at every boundary. Triggers: "validate handoff", "check the spec", "verify the plan".