Use when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or dependencies - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates
Builds and deploys containers using Podman. Covers multi-stage builds, rootless containers, Compose workflows, and systemd Quadlet integration. Use when creating Containerfiles, setting up container deployments, or configuring container orchestration.
[50] EXECUTE. Execute plans step-by-step with confirmation gates. Each step requires user approval before proceeding. Includes change management lifecycle (Pre-Change → During → Post-Change → Rollback). Use when implementing approved plans, deploying changes, or any multi-step execution requiring control and reversibility.
Executes implementation plans by dispatching agents based on step dependencies, following TDD with tests written before implementation
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
This skill should be used when claiming a task is "done", "complete", "finished", "fixed", "passing", or before committing. Requires running verification commands before making success claims.
Required workflow for AEM EDS development - linting, testing, preview validation, and PRs with demo links. Use when developing blocks or features for AEM Edge Delivery Services projects, before doing anything else.
Internal worker for pr-review skill. Claims file partitions, fixes comments, resolves threads. NOT for direct user invocation. Spawned only by pr-review orchestrator.
Use when you have a spec or requirements for a multi-step task, before touching code
Pre-deployment verification checklist covering build health, migrations, feature flags, rollback readiness, and environment parity. Use before deploying to production, after major features, or when preparing releases.
Gestión eficiente de tokens, detección de context bloat, planificación multi-run y validación pre-Done. Previene runs truncadas o incompletas.
Validate Phase II specifications for completeness, internal consistency, and readiness before implementation begins. Use when (1) Creating or reviewing Phase II specs (specs/<feature>/spec.md), (2) Preparing to implement a feature and need to verify spec quality, (3) Running spec review ceremonies, or (4) Ensuring spec-authority gate passes before proceeding with implementation.
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Follows TDD methodology.
Design and generate Azure Pipelines YAML scripts that comply with the latest standards based on official Microsoft documentation and project requirements. Prioritize using modular Templates.
Help users evaluate whether an MCP (Model Context Protocol) tool is safe and right for them before installing it. Use when a user wants to check, scan, review, or assess a third-party MCP server from GitHub, npm, or any repository URL. Provides plain-language assessments that anyone can understand, with technical details available on request.
Use when (1) deploying web application to Vercel staging or production, (2) monitoring deployment progress, (3) running post-deployment verification. Manages Vercel deployment workflow with safety checks.
Deploy current develop branch to production. Use when user says /deploy, "deploy to production", "push to heroku", "release to production", "deploy changes", "ship it", or "release changes". Commits changes, pushes develop, merges to main, creates version tag, pushes to GitHub and Heroku, then returns to develop branch.
Approve pending GitHub Actions workflows and add /ok-to-test comments to PRs that need testing
Comprehensive validation of collector bot packages using 8 parallel specialized agents. Use to validate existing collector packages for compliance.
Use when (1) preparing a release for staging or production, (2) generating release notes and changelog, (3) verifying environment readiness before deployment. Prepares all artifacts needed for a release.
