Design, discover, and refactor multi-command workflows for Claude Code
Designs multi-command workflows to guide users through complex processes.
/plugin marketplace add bryonjacob/aug/plugin install aug-core@augThis skill inherits all available tools. When active, it can use any tool Claude has access to.
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.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.