pipeline

Orchestrate and resume YAML-defined pipelines by name for Go and Next.js releases.

13|6|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/baekenough/second-brain --skill pipeline-baekenough
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/pipeline
Command: npx skills add https://github.com/baekenough/second-brain --skill pipeline-baekenough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates and resumes YAML-defined pipelines by name, enabling consistent, auditable release workflows across teams.

Core Features & Use Cases

  • End-to-end orchestration of pipelines defined in YAML, including resume-on-failure and parallel execution.
  • Validation of pipeline structure, verification of referenced skills, and robust state tracking for traceability.
  • Applicable to multi-repo release campaigns and complex Go/Next.js deployments with clear run visibility.

Quick Start

Invoke the pipeline by name to run the full release workflow, for example using /pipeline auto-dev.

Frequently Asked Questions about pipeline

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

FAQPage Schema
How do I orchestrate and resume YAML pipelines by name?

You can orchestrate YAML pipelines by invoking them by name, which executes stages from triage through release. It maintains per-run state, enabling workflows to resume on failure for consistent recovery and auditing.

Does this pipeline orchestration tool support Go and Next.js release workflows?

Yes, this pipeline orchestration tool is specifically applicable to Go and Next.js release workflows. It handles end-to-end deployment execution, including multi-repo release campaigns with clear run visibility and state tracking.

How do I validate pipeline structure and resolve skill invocations in YAML?

Validating pipeline structure and verifying referenced skills are built-in functions. It resolves skill invocations during execution and enforces structural validation to ensure your YAML-defined pipeline stages operate correctly.

Can I run parallel execution stages in my YAML release pipelines?

Yes, you can run parallel execution stages in YAML release pipelines. The orchestration engine supports parallel execution alongside robust state tracking to maintain traceability across complex multi-repo deployments.

What is the best way to manage multi-repo release campaigns with state tracking?

The best way to manage multi-repo release campaigns is using YAML-defined pipelines with per-run state tracking. This approach maintains auditable traceability, verifies referenced skills, and supports resume-on-failure for reliable deployments.