repo-defining-workflows

What problem does it solve?

Ad-hoc multi-agent workflow definitions lead to inconsistent YAML syntax, unclear agent coordination, missing validation criteria, and unreusable orchestration processes that fail to deliver expected outcomes.

Core Features & Use Cases

• Standardized YAML Structure: Provides a consistent frontmatter template (name, description, tags, status, agents, parameters) to ensure all workflow documents are valid, discoverable, and properly configured.
• Execution Pattern Guidance: Defines clear patterns for sequential, parallel, and conditional agent coordination, eliminating common errors like incorrect dependency ordering or unmanaged parallel execution.
• Validation Templates: Includes Gherkin-formatted success criteria templates to define clear, testable outcomes for workflow execution.
• Use Case Example: A team building a code review and deployment pipeline can use this skill to define a reusable workflow that coordinates a maker agent to generate changes, a checker agent to validate changes, and a fixer agent to resolve issues, with explicit phase dependencies and success checks.

Quick Start

Use the repo-defining-workflows skill to create a new multi-agent workflow document for your team's code review process, including all required YAML frontmatter, execution phases, and Gherkin success criteria.