workflow-authoring

Guides authoring of Claude Code workflow files that orchestrate commands, agents, and skills.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill workflow-authoring-rorysullivan1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-authoring
Source: https://github.com/RorySullivan1/powerapp_taskmaster/tree/main/.claude/skills/workflow-authoring
Command: npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill workflow-authoring-rorysullivan1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step automation recipes often fail because they lack clear stop conditions, loop exits, branch logic, and approval gates, causing workflows to wander, loop forever, or fire irreversible actions without asking. This Skill provides the design discipline and structure needed to write reliable Claude Code workflow definitions. ## Core Features & Use Cases - Layer selection guidance: Decide whether a task warrants a workflow versus a command, agent, or skill before writing anything. - Structured workflow anatomy: Enforces purpose lines, inputs/outputs, ordered steps with asset references and hand-offs, control flow, STOP conditions, and an Invokes manifest. - Safety gates and anti-patterns: Requires approval gates on irreversible actions and flags common failures like unbounded loops, restated mandates, and chat-only state. - Use Case: You want to automate a release pipeline that verifies a build, tags a version, and opens a PR. Use this Skill to scaffold the workflow file with explicit success, bail, and gate conditions for each step. ## Quick Start Ask the assistant to author a workflow that orchestrates your chosen commands and agents into a multi-step pipeline with explicit stop conditions.

Frequently Asked Questions about workflow-authoring

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

FAQPage Schema
How do I write a Claude Code workflow file?▼

Create a markdown file in .claude/workflows/ with a purpose line, inputs and outputs, numbered steps that each invoke an existing command, agent, or skill by path, a control flow section with STOP conditions, and an Invokes manifest listing every referenced asset.

When should I use a workflow vs a command or agent?▼

Use a workflow for deterministic multi-step control flow that loops, branches, or spawns agents and runs mostly unattended. Use a command for a single one-shot prompt, an agent for an isolated side task, and a skill for reusable in-session expertise.

Why does my workflow loop forever or never stop?▼

Workflows fail when loops lack a terminal state or steps lack success and failure criteria. Every loop must name what ends it, such as a counter or empty queue, and every step needs an explicit done condition and bail behavior.

How do I prevent a workflow from running irreversible actions?▼

Place an explicit approval gate before any outward-facing or hard-to-undo step such as opening a PR, posting, sending, deleting, or deploying. The gate can be a human checkpoint or a precondition that must hold before the action fires.

What are the limitations of a workflow markdown file?▼

A workflow markdown file is a declarative recipe the model follows with judgment, not a deterministic runtime that scripts parallel execution. It orchestrates existing assets rather than doing the domain work itself, so each step must reference a real command, agent, or skill.