How do I install the Workflow Design skill?

Run npx skillmds@latest add majiayu000/workflow-design in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Workflow Design skill do?

Design, discover, and refactor multi-command workflows for Claude Code It is listed under Productivity, Marketing & Growth on SkillMD.

Is Workflow Design safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Workflow Design?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Workflow Design free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Workflow Design?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Workflow Design by majiayu000 — Agent Skill

Name: Workflow Design
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Workflow Design Skill

Define multi-command workflows that guide users through complex processes.

Core Concepts

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.

Three Modes

1. Discovery Mode

When: Have related commands, need to identify workflow.

Process: List commands -> identify sequence -> find phase boundaries -> determine dependencies -> generate workflow doc -> update command metadata.

2. Design Mode

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.

3. Refactor Mode

When: Workflow exists but needs improvement.

Analyze: Completeness, ordering, clarity, consistency. Output updated docs and migration notes.

Workflow Document Template

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]

Command-Workflow Metadata

Commands reference workflows BELOW frontmatter:

**Workflow:** [workflow-name] - **Phase:** phase-name (step X/Y) - **Next:** /next-command

Phase Design Principles

Clear Boundaries: Distinct purpose, defined outputs, obvious transitions
Single Responsibility: One thing well per phase
Checkpoints: Interactive phases validate progress
Automation-Friendly: Questions answerable from codebase

Workflow Patterns

Linear: Phase 1 -> Phase 2 -> Phase 3 -> Done
Loop: Phase 1 -> Phase 2 -> (repeat Phase 2) -> Done
Branching: Phase 1 -> (choice) -> Phase 2a OR 2b -> Done
Parallel: Phase 1 -> (2a + 2b parallel) -> Phase 3 -> Done

Naming

Good: epic-development.md, database-migration.md, feature-release.md

Bad: stuff.md, the-way-we-do-things.md, process-1.md

Key Principle

Workflows document existing patterns, they don't invent them. Commands remain primary. Workflows organize them. User stays in control.

---name: workflow-designdescription: Design, discover, and refactor multi-command workflows for Claude Code--- # Workflow Design Skill Define multi-command workflows that guide users through complex processes. ## Core Concepts **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. ## Three Modes ### 1. Discovery Mode **When:** Have related commands, need to identify workflow. **Process:** List commands -> identify sequence -> find phase boundaries -> determine dependencies -> generate workflow doc -> update command metadata. ### 2. Design Mode **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. ### 3. Refactor Mode **When:** Workflow exists but needs improvement. **Analyze:** Completeness, ordering, clarity, consistency. Output updated docs and migration notes. ## Workflow Document Template Location: `workflows/[workflow-name].md` ```markdown # [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] ``` ## Command-Workflow Metadata Commands reference workflows BELOW frontmatter: ```markdown **Workflow:** [workflow-name] - **Phase:** phase-name (step X/Y) - **Next:** /next-command ``` ## Phase Design Principles 1. **Clear Boundaries:** Distinct purpose, defined outputs, obvious transitions 2. **Single Responsibility:** One thing well per phase 3. **Checkpoints:** Interactive phases validate progress 4. **Automation-Friendly:** Questions answerable from codebase ## Workflow Patterns - **Linear:** Phase 1 -> Phase 2 -> Phase 3 -> Done - **Loop:** Phase 1 -> Phase 2 -> (repeat Phase 2) -> Done - **Branching:** Phase 1 -> (choice) -> Phase 2a OR 2b -> Done - **Parallel:** Phase 1 -> (2a + 2b parallel) -> Phase 3 -> Done ## Naming Good: `epic-development.md`, `database-migration.md`, `feature-release.md` Bad: `stuff.md`, `the-way-we-do-things.md`, `process-1.md` ## Key Principle Workflows document existing patterns, they don't invent them. Commands remain primary. Workflows organize them. User stays in control.

Frequently asked questions

Workflow Design