cicd
24
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
zenobi-us
devops
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
cicd
24
deployment-engineer
Expert deployment engineer specializing in CI/CD pipelines, release automation, and deployment strategies. Masters blue-green, canary, and rolling deployments with focus on zero-downtime releases and rapid rollback capabilities.
zenobi-us
devops
cicd
24
writing-skills
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
lifangda
devops
cicd
23
tech-lead
Technical Lead that implements code ONE FILE AT A TIME to prevent crashes. Handles code review, best practices, mentorship, implementation planning. **CRITICAL CHUNKING RULE - Large implementations (auth system = auth.ts + tests + middleware) done incrementally.** Activates for tech lead, code review, best practices, refactoring, technical debt, code quality, design patterns, SOLID principles, clean code, code standards, implementation plan, technical guidance, mentorship, code optimization, complexity analysis, technical planning, estimation, implementation strategy, code architecture.
anton-abyzov
devops
cicd
23
release-coordinator
Coordinates multi-component releases, feature flags, versioning, and rollback strategies. Trigger terms: release management, release planning, release coordination, feature flags, canary deployment, progressive rollout, release notes, rollback strategy, release train, deployment coordination, versioning, changelog, release approval, deployment checklist. Manages complex release workflows: - Multi-component release coordination - Feature flag strategy and management - Versioning and changelog generation - Canary and blue-green deployments - Progressive rollout strategies - Rollback procedures - Release approval workflows - Post-release verification Use when: planning releases, coordinating multi-service deployments, managing feature flags, or generating release notes.
nahisaho
devops
cicd
23
rc-manager
Manages Release Candidate (RC) workflows including pre-release tagging, RC lifecycle (alpha/beta/rc), testing validation, RC promotion to production, rollback procedures, and channel-based releases. Handles RC versioning (v1.0.0-rc.1, v1.0.0-beta.1), tracks RC testing status, coordinates RC across multiple repositories, manages canary/blue-green deployments. Activates for release candidate, RC, pre-release, beta release, alpha release, canary release, rc workflow, promote rc, rc testing, staging release, pre-production.
anton-abyzov
devops
cicd
23
multi-project-spec-mapper
Intelligent multi-project specification splitting and organization. Analyzes user stories to map them to correct projects (FE, BE, MOBILE, INFRA) based on content, tech stack, and component architecture. Creates project-specific folder structure and splits monolithic specs. Activates for multi-project JIRA/GitHub setups, brownfield projects with multiple teams, microservices architecture. Keywords: multi-project, project mapping, spec splitting, JIRA projects, multiple projects, microservices, FE/BE/MOBILE split, intelligent classification.
anton-abyzov
devops
cicd
23
release-coordinator
Coordinates multi-component releases, feature flags, versioning, and rollback strategies. Trigger terms: release management, release planning, release coordination, feature flags, canary deployment, progressive rollout, release notes, rollback strategy, release train, deployment coordination, versioning, changelog, release approval, deployment checklist. Manages complex release workflows: - Multi-component release coordination - Feature flag strategy and management - Versioning and changelog generation - Canary and blue-green deployments - Progressive rollout strategies - Rollback procedures - Release approval workflows - Post-release verification Use when: planning releases, coordinating multi-service deployments, managing feature flags, or generating release notes.
nahisaho
devops
cicd
23
mlops-dag-builder
Design DAG-based MLOps pipeline architectures with Airflow, Dagster, Kubeflow, or Prefect. Activates for DAG orchestration, workflow automation, pipeline design patterns, CI/CD for ML. Use for platform-agnostic MLOps infrastructure - NOT for SpecWeave increment-based ML (use ml-pipeline-orchestrator instead).
anton-abyzov
devops
cicd
23
role-orchestrator
Multi-agent orchestration system that coordinates specialized agents (PM, Architect, DevOps, QA, Tech Lead, Security) to work together on complex tasks. Implements hierarchical orchestrator-worker pattern. Activates for complex multi-step requests requiring multiple roles/skills. Keywords: build product, create SaaS, full implementation, end-to-end, multi-agent, orchestrate, coordinate roles, complex project.
anton-abyzov
devops
cicd
23
deploy-router
Smart deployment platform router for Vercel vs Cloudflare vs GitHub Pages. Analyzes project structure, framework, SEO needs, runtime requirements, AND repository visibility (private/public). Routes to Cloudflare for private repos (GitHub Pages requires paid plan), Vercel for dynamic SEO, GitHub Pages only for public repos. Activates for deploy, vercel vs cloudflare, where to deploy, cloudflare workers, cloudflare pages, vercel deployment, edge deployment, SSR deployment, static site deployment, which hosting, deployment recommendation, github pages, private repo deployment.
anton-abyzov
devops
cicd
23
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing
withzombies
devops
cicd
23
resonance-devops
DevOps Engineer Specialist. Use this for CI/CD pipelines, Infrastructure as Code, and SRE/monitoring.
manusco
devops
cicd
23
dependency-analysis
Analyze project dependencies for security vulnerabilities, outdated packages, and upgrade paths. Use when auditing dependencies or planning upgrades.
vneseyoungster
devops
cicd
23
review-implementation
Use after hyperpowers:executing-plans completes all tasks - verifies implementation against bd spec, all success criteria met, anti-patterns avoided
withzombies
devops
cicd
23
constitution-enforcer
Validates compliance with 9 Constitutional Articles and Phase -1 Gates before implementation. Trigger terms: constitution, governance, compliance, validation, constitutional compliance, Phase -1 Gates, simplicity gate, anti-abstraction gate, test-first, library-first, EARS compliance, governance validation, constitutional audit, compliance check, gate validation. Enforces all 9 Constitutional Articles with automated validation: - Article I: Library-First Principle - Article II: CLI Interface Mandate - Article III: Test-First Imperative - Article IV: EARS Requirements Format - Article V: Traceability Mandate - Article VI: Project Memory - Article VII: Simplicity Gate - Article VIII: Anti-Abstraction Gate - Article IX: Integration-First Testing Runs Phase -1 Gates before any implementation begins. Use when: validating project governance, checking constitutional compliance, or enforcing quality gates before implementation.
nahisaho
devops
cicd
23
default-tech-stack
Default technology stack for Gaia projects. Use when starting new projects, making tech decisions, or setting up infrastructure. These are defaults and as such, any specific user mandates for any of the below areas, should be honored.
frostaura
devops
cicd
23
finishing-a-development-branch
Use when implementation complete and tests pass - closes bd epic, presents integration options (merge/PR/keep/discard), executes choice
withzombies
devops
cicd
23
verification-before-completion
Use before claiming work complete, fixed, or passing - requires running verification commands and confirming output; evidence before assertions always
withzombies
devops
cicd
23
constitution-enforcer
Validates compliance with 9 Constitutional Articles and Phase -1 Gates before implementation. Trigger terms: constitution, governance, compliance, validation, constitutional compliance, Phase -1 Gates, simplicity gate, anti-abstraction gate, test-first, library-first, EARS compliance, governance validation, constitutional audit, compliance check, gate validation. Enforces all 9 Constitutional Articles with automated validation: - Article I: Library-First Principle - Article II: CLI Interface Mandate - Article III: Test-First Imperative - Article IV: EARS Requirements Format - Article V: Traceability Mandate - Article VI: Project Memory - Article VII: Simplicity Gate - Article VIII: Anti-Abstraction Gate - Article IX: Integration-First Testing Runs Phase -1 Gates before any implementation begins. Use when: validating project governance, checking constitutional compliance, or enforcing quality gates before implementation.
nahisaho
devops
cicd
21
bun-docker
Use for Docker with Bun, Dockerfiles, oven/bun image, containerization, and deployments.
secondsky
devops
cicd
21
vulnerability-scanning
Automated security scanning for dependencies, code, containers with Trivy, Snyk, npm audit. Use for CI/CD security gates, pre-deployment audits, compliance requirements, or encountering CVE detection, outdated packages, license compliance, SBOM generation errors.
secondsky
devops
cicd
20
ci-cd-optimizer
Optimize CI/CD pipelines for speed, reliability, and efficiency. Use when improving build times, fixing pipeline failures, or enhancing deployment processes.
armanzeroeight
devops
cicd
20
decision-engine
Autonomous decision-making engine for technical choices in technology selection, architecture patterns, and task ordering. Use when Maestro orchestrator needs to make decisions without human input for choosing libraries/frameworks based on existing codebase, selecting architectural patterns based on complexity and requirements, and optimizing task execution order based on dependency analysis. Analyzes codebase context, applies scoring rubrics, and returns structured decisions with rationale.
ll931217
devops