CI/CD
13574 skills in DevOps > CI/CD
meddic-checklist
Use to inspect qualification coverage across Metrics, Economic buyer, Decision criteria, Decision process, Implications, Champion.
instrumentation
Use when defining events, fields, and governance for GTM analytics pipelines.
diagnostics
Use for structured technical SEO audits, incident response, and validation.
exec-briefing
Use to craft concise executive updates, agendas, and follow-up logs for QBR/EBR sessions.
save-play-library
Use to catalog churn/expansion plays tied to specific signals, cohorts, and owners.
creative-iteration-playbook
Framework for briefing, testing, and scaling social creative variations.
deal-review
Use to run structured opportunity inspections that align pipeline data with buyer reality.
crm-hygiene
Use to enforce stage definitions, next-step requirements, and data completeness across the pipeline.
calendar-governance
Use to enforce cadence rules, timezone coverage, and operational controls on social calendars.
cohort-analysis
Standard method for slicing bookings, pipeline, and retention cohorts for diagnostics.
decision-trees
Use when designing branching logic, eligibility rules, and fallback paths.
nextjs
Guide for implementing Next.js - a React framework for production with server-side rendering, static generation, and modern web features. Use when building Next.js applications, implementing App Router, working with server components, data fetching, routing, or optimizing performance.
capacity-modeling
Use to model bookings targets vs headcount, ramp, and productivity assumptions.
creative-brief-framework
Use to structure concise creative briefs with goals, audience, and guardrails.
advocate-sourcing
Use to identify, score, and prioritize customer advocates for programs.
drip-campaigns
Use when you need to map sequenced nurture flows with pacing, storytelling arcs, and value ladders.
specswarm-ship
Systematic quality validation, test verification, and safe merging workflow for deployment/release operations. ALWAYS asks for confirmation when user wants to ship, deploy, merge, release, or complete features to production, merge to main branch, or finalize features. This is a DESTRUCTIVE operation (merges and deletes branches).
specswarm-build
Systematic spec-driven workflow (specification→clarification→planning→tasks→implementation→validation) for feature development. Auto-executes when user clearly wants to build, create, add, implement, develop, make, construct, or set up software features, components, or functionality.
exec-briefing-kit
Template for packaging revenue analytics into concise exec/board narratives.
waterfall-blueprint
Use to design provider sequences, throttling logic, and credit policies for enrichment waterfalls.