default-workflow

Automate multi-file development workflows from requirements through merge.

1|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/rysweet/AzureHayMaker --skill default-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: default-workflow
Source: https://github.com/rysweet/AzureHayMaker/tree/main/.claude/skills/default-workflow
Command: npx skills add https://github.com/rysweet/AzureHayMaker --skill default-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a consistent, canonical development workflow for non-trivial code changes, coordinating specialized agents from requirements to merge.

Core Features & Use Cases

  • End-to-end workflow orchestration with defined stages
  • Coordination of domain-specific agents (design, build, test, review, merge)
  • Single source of truth to prevent drift between interface and canonical process

Quick Start

Trigger the default workflow for multi-file changes to ensure quality and consistency.

Frequently Asked Questions about default-workflow

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

FAQPage Schema
How do I automate a multi-file code change workflow from requirements to merge?

The default workflow automates end-to-end orchestration for multi-file changes, coordinating specialized agents through requirements clarification, design, implementation, testing, review, and merge stages. It enforces a canonical process to prevent drift and ensure consistency across complex refactoring or significant integrations.

When should I use a structured development workflow for code changes?

Use a structured workflow for non-trivial changes affecting 5+ files, complex integrations, or significant refactoring. It maintains a single source of truth, coordinates domain-specific agents at each stage, and ensures quality gates are applied consistently before merge.

Can I coordinate multiple specialized agents through a single workflow?

Yes. The workflow orchestrates domain-specific agents for design, build, test, review, and merge stages, eliminating duplication and ensuring each specialist operates from the same canonical requirements and design.

What prevents drift between workflow stages in a multi-file implementation?

A single canonical source of truth tracks requirements, design decisions, and implementation progress across all stages. Specialized agents reference this shared state, preventing inconsistencies and ensuring coordinated execution from clarification through merge.

How does this workflow handle architecture changes affecting multiple files?

The workflow enforces stepwise execution through design and review before implementation, ensuring architectural decisions are validated early. Complex integrations are coordinated across specialized agents, with testing and review gates applied before merge.