vela-stages

Manage parallel execution and dependencies for Vela CI/CD stages.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/ryanmr/vela-skills --skill vela-stages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vela-stages
Source: https://github.com/ryanmr/vela-skills/tree/main/.agents/skills/vela-stages
Command: npx skills add https://github.com/ryanmr/vela-skills --skill vela-stages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for efficient parallel execution of tasks within CI/CD pipelines, enabling faster build and deployment cycles by running independent jobs concurrently.

Core Features & Use Cases

  • Parallel Stage Execution: Run multiple stages of your pipeline simultaneously to reduce overall build time.
  • Dependency Management: Define explicit dependencies between stages using the needs key, ensuring correct execution order.
  • Stage Isolation: Use the independent key to prevent a stage's failure from halting unrelated parallel stages, crucial for monorepos.
  • Compile-Time Pruning: Understand how rulesets can cause entire stages to be removed before execution, and how to manage needs dependencies accordingly.
  • Use Case: In a monorepo, you can have separate stages for building and testing the backend and frontend applications, running them in parallel. A subsequent deployment stage would then wait for both to complete successfully.

Quick Start

Use the vela-stages skill to define a pipeline with two parallel stages, 'build' and 'test', where 'deploy' depends on both.

Frequently Asked Questions about vela-stages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run CI/CD stages in parallel to reduce build time?

Vela stages allow you to run multiple CI/CD stages simultaneously, executing independent jobs concurrently to reduce overall build and deployment time in your pipeline.

How do I define dependencies between pipeline stages so they execute in order?

Dependencies between pipeline stages are defined using the `needs` key, ensuring correct execution order by making a downstream stage wait for its required upstream stages to complete successfully.

Can I isolate a stage so its failure doesn't halt unrelated parallel jobs in a monorepo?

Yes, stage isolation is achieved using the `independent` key, which prevents a specific stage's failure from halting unrelated parallel stages, an approach particularly useful for monorepo pipelines.

Why does my Vela pipeline fail when a dependency is removed by compile-time pruning?

Rulesets can cause entire stages to be removed before execution during compile-time pruning, which impacts pipeline execution flow and can break `needs` dependencies if not managed accordingly.

What is the best way to structure a monorepo pipeline with parallel build and deploy stages?

In a monorepo, you can define separate parallel stages for building and testing different applications, and then configure a subsequent deployment stage with `needs` to wait for both to complete successfully.

When should I use the independent flag for parallel execution in Vela?

Use the `independent` flag when running parallel stages where you want to prevent a failure in one isolated stage, such as a specific monorepo service test, from halting unrelated concurrent pipeline jobs.