dryrun

Orchestrate Human, Dev, and Auditor agents to validate pipeline workflows across versions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gapfDev/workflow --skill dryrun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dryrun
Source: https://github.com/gapfDev/workflow/tree/main/.claude/skills/dryrun
Command: npx skills add https://github.com/gapfDev/workflow --skill dryrun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dry-run orchestration decouples testing from real code changes by coordinating multiple agents to validate end-to-end pipelines in a safe, isolated workspace.

Core Features & Use Cases

  • Orchestrates three specialized agents (Human, Dev, Auditor) to simulate a complete pipeline flow.
  • Discovers and validates pipeline structure from a given version, generating phase-boundaries, checklists, and artifacts.
  • Ensures safe, versioned testing with isolated workspaces and artifact reuse rules.

Quick Start

Run the dryrun orchestrator with a version argument and a synthetic ticket to start the multi-agent dry-run.

Frequently Asked Questions about dryrun

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

FAQPage Schema
What is an end-to-end dry-run validation for pipeline workflows?

End-to-end dry-run validation decouples testing from real code changes by simulating a complete pipeline flow in an isolated workspace to safely verify pipeline structure, stoppers, and artifacts.

How do I automate pipeline testing across different versions?

You automate pipeline testing by running an agent-based orchestrator with a specific version argument, which discovers the pipeline and creates an isolated temp workspace, ticket metadata, and a per-run checklist.

Does pipeline dry-run testing require any specific dependencies?

No specific dependencies are required. The orchestration relies on coordinating multiple specialized agents to validate versioned sources within an isolated environment rather than requiring external modules.

Can I use a multi-agent approach to verify pipeline artifacts?

Yes, you can use a multi-agent approach. The orchestration coordinates three specialized agents—Human, Dev, and Auditor—to simulate the pipeline flow, validate phase boundaries, and enforce artifact reuse rules.

What is the best way to safely test pipeline structure without changing code?

The best way is running an agent-based dry-run orchestrator that generates phase boundaries, checklists, and artifacts in an isolated temp workspace, ensuring safe verification without altering real code.