Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates
Test agent delegation patterns to verify hierarchy and escalation paths. Use after modifying agent structure.
Run local builds with proper environment setup. Use when building code locally to verify changes before pushing.
DevSecOps methodology guidance covering shift-left security, SAST/DAST/IAST integration, security gates in CI/CD pipelines, vulnerability management workflows, and security champions programs.
Validate code review feedback against implementation plan to prevent scope creep and derailment
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches cipherpowers:code-review-agent subagent to review implementation against plan or requirements before proceeding
Harden configuration and defaults for safer deployment. Use when a mid-level developer needs to reduce misconfig risks.
Diagnose and verify Parade project setup. Checks all required components and reports issues.
Plan safe dependency upgrades with risk notes. Use when a mid-level developer is tasked with upgrading libraries.
Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.
Create a plan to migrate platforms or runtimes. Use when a senior developer needs a phased migration approach.
Check and manage .env configuration for docker-local projects - conflict detection, unique IDs, isolation settings
Run section orchestrators to coordinate multi-component workflows. Use when starting work on a section.
Diagnose CI failures and stabilize pipelines. Use when a mid-level developer needs to resolve flaky or failing builds.
Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage.
Audit codebase for agentic layer coverage and identify gaps. Use when assessing agentic layer maturity, identifying investment opportunities, or evaluating primitive coverage.
Plan feature flag rollout and cleanup. Use when a mid-level developer needs controlled release guidance.
Parse and analyze CI failure logs to identify root causes and error patterns. Use when CI builds fail to understand what broke.
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
Configure issue classification for ADWs to route work to the correct templates. Use when setting up automatic classification of GitHub issues into chores, bugs, and features.
Validates BAZINGA completion claims with independent verification. Spawned ONLY when PM sends BAZINGA. Acts as final quality gate - verifies test failures, coverage, evidence, and criteria independently. Returns ACCEPT or REJECT verdict.
Validate and verify dependencies are available and compatible. Use when setting up environments.
Master orchestrator that generates all implementation specs (PRD, Architecture, UX, Implementation, Test, Release) from product plan. Use when generating complete specification package.
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
