Design, discover, and refactor multi-command workflows for Claude Code
/plugin marketplace add bryonjacob/aug/plugin install bryonjacob-aug-core-aug-core@bryonjacob/augThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Help define multi-command workflows that guide users through complex processes. Workflows are sequences of commands that accomplish a larger goal, with each command representing a discrete phase.
Workflow: A documented sequence of commands that accomplish a goal.
Components:
Not a workflow:
Command: Single discrete action
/plan-chat, /plan-breakdown, /workWorkflow: Sequence of commands with shared goal
epic-development workflow uses /plan-chat → /plan-breakdown → /plan-create → /work✅ Multi-step processes with clear phases
✅ Processes users repeat
✅ Processes with decision points
❌ Bad workflow candidates:
When: You have related commands, need to identify the workflow
Process:
Example:
Input: /plan-chat, /plan-breakdown, /plan-create, /work commands
Output: epic-development workflow document
When: Designing a new multi-step process from scratch
Process:
Example:
Input: "Need workflow for database migration"
Output: migration-workflow.md + command stubs
When: Workflow exists but needs improvement
Process:
Example:
Input: existing deployment-workflow.md
Output: Improved workflow with added verification phase
Location: workflows/[workflow-name].md
Template:
# [Workflow Name]
## Overview
[1-2 sentence description of goal]
## When to Use
- [Use case 1]
- [Use case 2]
## Phases
### 1. [Phase Name] (interactive/automated)
- **Command:** /command-name
- **Purpose:** What this phase accomplishes
- **Output:** What it produces
- **Requires:** Dependencies (optional)
- **Repeatable:** yes/no (optional)
### 2. [Next Phase]
...
## Execution
**Manual (step-by-step):**
```bash
/command1
/command2
/command3
Automated (full workflow):
/workflow-run [workflow-name]
Hybrid (check progress):
/workflow-status [workflow-name]
## Command-Workflow Metadata
Commands reference workflows BELOW frontmatter:
```markdown
---
name: command-name
description: What command does
---
**Workflow:** [workflow-name](../../aug-core/workflows/workflow-name.md) • **Phase:** phase-name (step X/Y) • **Next:** /next-command
[rest of command]
Key elements:
Given: Set of related commands Goal: Identify and document the workflow
Steps:
List commands and their purposes
/plan-chat - Interactive design session
/plan-breakdown - Decompose into tasks
/plan-create - Generate GitHub issues
/work - Execute task
Identify natural sequence
Group into phases
Planning Phase:
- /plan-chat
- /plan-breakdown
- /plan-create
Execution Phase:
- /work (repeatable per task)
Extract patterns
Generate workflow document
workflows/[name].mdUpdate command metadata
Given: Description of needed workflow Goal: Create new workflow and commands
Steps:
Clarify the goal
Break into phases
Identify decision points
Create workflow document
Scaffold commands
Implement commands
Given: Existing workflow Goal: Improve structure and clarity
Analysis questions:
Completeness
Ordering
Clarity
Consistency
Output:
Pattern: [goal]-workflow.md or [domain].md
Good names:
epic-development.md - Clear goaldatabase-migration.md - Specific domainfeature-release.md - Understandable processBad names:
stuff.md - Too vaguethe-way-we-do-things.md - Too wordyprocess-1.md - No meaningEach phase should have:
Phase does ONE thing well:
Interactive phases are natural checkpoints:
Phases should be automatable with context:
Apply hemingwayesque principles to workflow docs:
Before: "This phase is designed to help you interactively work through the architectural design decisions that need to be made."
After: "Interactive architecture design session. Output: design decisions, component breakdown."
Phase 1 → Phase 2 → Phase 3 → Done
Example: epic-development
Phase 1 → Phase 2 → Phase 3 → (repeat Phase 3) → Done
Example: task execution (work on multiple tasks)
Phase 1 → (choice) → Phase 2a OR Phase 2b → Phase 3 → Done
Example: project setup (different stacks)
Phase 1 → (Phase 2a + Phase 2b in parallel) → Phase 3 → Done
Example: setup (install deps + configure tools)
Workflows document existing patterns, they don't invent them. Good workflows emerge from observing how users actually accomplish goals, then formalizing that sequence for reuse and automation.
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.