kienbui1995/magic-powers/ado-pipeline-design
Claude Code and agent skill by kienbui1995/magic-powers
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Use when designing Azure Pipelines YAML — multi-stage pipelines, reusable templates, conditions and expressions, matrix strategies, triggers, and pipeline dependencies for complex CI/CD workflows.
Install
npx vskill@latest install kienbui1995/magic-powers/ado-pipeline-designSKILL.md
The same SKILL.md was published earlier as kienbui1995/magic-powers/ado-pipeline-design.
ADO Pipeline Design
When to Use
- Designing a new CI/CD pipeline for an application
- Refactoring a spaghetti pipeline to multi-stage YAML
- Creating reusable templates for multiple repos
- Setting up matrix builds for multiple platforms/versions
- Configuring complex trigger conditions
Core Jobs
1. Multi-Stage Pipeline Structure
2. Reusable Templates
Template types:
- Step templates — reusable steps across jobs
- Job templates — reusable entire jobs
- Stage templates — reusable entire stages (most powerful, best for org-wide reuse)
- Variable templates — shared variable definitions across pipelines
3. Conditions & Expressions
4. Matrix Strategy
5. Pipeline Dependencies & Stage Outputs
Key Concepts
- Stage — logical phase (Build, Test, Deploy); each stage can have multiple jobs
- Job — runs on one agent; steps execute sequentially within a job
- Template — reusable YAML fragment; parameterized for flexibility; can be in same repo or a templates repo
- Condition — expression controlling if stage/job/step runs; defaults to
succeeded() - Matrix — runs the same job with different variable values in parallel; controlled by
maxParallel - Stage output — pass computed values between stages using
stageDependencies+isOutput=true - Deployment job — special job type with
environmentand deploymentstrategy(runOnce, rolling, canary)
Checklist
- [ ] Stages reflect logical phases (Build, Test, Deploy Dev, Deploy Prod) not technical steps?
- [ ] Shared logic extracted to templates (not copy-pasted across pipelines)?
- [ ] Conditions prevent unnecessary deploys (check branch, check previous stage success)?
- [ ] Pipeline artifacts used to pass build output between stages (not rebuilding in deploy)?
- [ ] PR triggers exclude draft PRs and docs-only changes (use
paths.exclude)? - [ ] Stage outputs used where values need to cross stage boundaries (image tag, version)?
- [ ]
dependsOnexplicit for non-linear stage dependencies?
Key Outputs
- Multi-stage YAML pipeline with clear Build → Test → Deploy Dev → Deploy Prod stages
- Reusable templates extracted to
templates/directory and parameterized - Conditions preventing prod deploys from feature branches or failed builds
- Stage output variables threaded through pipeline (e.g. image tag from build to deploy)
Output Format
- 🔴 Critical — prod deploys without condition check (any branch can deploy to production), rebuilding code in deploy stage instead of using artifacts, secrets hardcoded in YAML variables
- 🟡 Warning — no templates (copy-paste pipeline YAML across repos), single-stage pipeline (no deployment separation), no PR trigger configuration (runs on every push including forks)
- 🟢 Suggestion — use matrix for multi-version/platform testing, extract common steps to stage templates, use stage outputs for image tags instead of re-querying registry
Anti-Patterns
- Downloading source code in deploy stage and rebuilding (always use pipeline artifacts — build once)
- Conditions using
==instead ofeq()(YAML expression syntax is different from standard comparison) - Single monolithic pipeline YAML file exceeding 500 lines (split into stage/job templates)
- No
pathsfilter on trigger (rebuilds on every commit including documentation changes) - Using
trigger: noneon a pipeline that should run on push (accidental manual-only pipeline)
Integration
ado-release-management— add gates and approvals to the deploy stages designed hereado-pipeline-optimization— optimize the build and test stages for speed and costado-pipeline-security— harden the pipeline designed here against secret exfiltration and unauthorized access
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/ado-pipeline-design/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kienbui1995/magic-powers/ado-pipeline-design)