From aug-core
Design, discover, and refactor multi-command workflows for Claude Code
How this skill is triggered — by the user, by Claude, or both
Slash command
/aug-core:skills/workflow-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Define multi-command workflows that guide users through complex processes.
Define multi-command workflows that guide users through complex processes.
Workflow: Documented sequence of commands accomplishing a goal.
Components: Workflow document + individual command files + command-workflow links.
Good candidates: Multi-step processes with clear phases, repeatable processes, processes with decision points.
Bad candidates: Single-step operations, rarely-used sequences, completely linear with no decisions.
When: Have related commands, need to identify workflow.
Process: List commands -> identify sequence -> find phase boundaries -> determine dependencies -> generate workflow doc -> update command metadata.
When: Creating new multi-step process from scratch.
Process: Clarify goal -> break into phases -> identify decision points -> create workflow doc -> scaffold command stubs -> implement commands.
When: Workflow exists but needs improvement.
Analyze: Completeness, ordering, clarity, consistency. Output updated docs and migration notes.
Location: workflows/[workflow-name].md
# [Workflow Name]
## Overview
[1-2 sentence goal]
## When to Use
- [Use case 1]
## Phases
### 1. [Phase Name] (interactive/automated)
- **Command:** /command-name
- **Purpose:** What it accomplishes
- **Output:** What it produces
- **Repeatable:** yes/no (optional)
## Execution
- Manual: /command1 -> /command2
- Automated: /workflow-run [workflow-name]
Commands reference workflows BELOW frontmatter:
**Workflow:** [workflow-name] - **Phase:** phase-name (step X/Y) - **Next:** /next-command
Good: epic-development.md, database-migration.md, feature-release.md
Bad: stuff.md, the-way-we-do-things.md, process-1.md
Workflows document existing patterns, they don't invent them. Commands remain primary. Workflows organize them. User stays in control.
npx claudepluginhub bryonjacob/aug --plugin aug-coreGuides designing workflow-based Claude Code skills with numbered phases, decision trees, subagent delegation, and progressive disclosure. For sequential pipelines, routing patterns, safety gates, task tracking, phased execution, or refactoring skills.
Generates the /process orchestrator command for a repo by writing .claude/commands/process.md that reads process-template.json and walks through configured workflow steps.
Guides a contributor from a workflow idea to a complete Workflow Implementation Packet with overlap analysis, Why Gate, and skill sequencing. Use when creating a new multi-skill workflow or promoting an ad-hoc chain into a durable one.