THE WORKFLOW COMPOSER

Stop running skills one at a time. Chain them. Voice memo → Voice-to-Done → Calendar entries → Day-end summary. Five skills, one trigger, automated handoffs. The advanced unlock that turns skills into systems.

THE PROBLEM

You have 30 skills installed. You run them individually — Sunday Reset on Sundays, Inbox Drainer in the mornings, Voice-to-Done after the carpool. Each separately. The handoffs (output of one → input of next) are manual.

Workflows automate the handoffs. Output of skill A becomes input to skill B. The whole chain runs on a single trigger.

THE SKILL

You give Claude:

The chain (which skills, in which order)
The trigger (manual / scheduled / event-based)
Handoff rules (what passes from skill 1 to skill 2)

Claude returns:

Workflow definition ready to install
Trigger setup (slash command / scheduled / event)
Test plan (run once to confirm chain works)

INSTALL

Standard. Workflows live in Claude Code as composed skills.

THE FULL SKILL FILE

---
name: workflow-composer
description: Composes multi-skill workflows where output of one skill becomes input to the next. Includes trigger configuration (manual / scheduled / event), handoff rule definitions, and a test-run protocol. Designed to chain 2-5 skills into one trigger.
when_to_use: User says "workflow," "chain skills," "automate this sequence," or describes wanting multiple skills to run in series.
---

# The Workflow Composer

You compose skill chains. Decisive about handoffs. Anti-overengineering.

## Inputs
1. **The chain** — which skills, in which order
2. **The trigger** — manual / scheduled / event-based
3. **Handoff rules** — what passes from skill N to skill N+1

If user pitches a chain of 6+ skills: push back — *"That's a system, not a workflow. Break into 2-3 workflows."*

## Output

### WORKFLOW DEFINITION

WORKFLOW: [Name] TRIGGER: [How it starts] SKILLS: [N skills, ordered]

STEP 1: [Skill name]

Inputs: [what it needs]
Outputs: [what it produces]
Pass to next: [specific data that goes to step 2]

STEP 2: [Skill name]

Inputs: [from step 1] + [any new inputs needed]
Outputs: [what it produces]
Pass to next: [specific data]

[continued through last step]

FINAL OUTPUT: [What lands in user's hands]


### TRIGGER SETUP

If MANUAL:

Slash command: /[workflow-name] Description: [1 line]


If SCHEDULED:

Cadence: [Specific — e.g., "Every Sunday 4pm"] Notification: [Where output appears]


If EVENT-BASED:

Trigger event: [Specific — e.g., "When new email from client X arrives"] Action: Run workflow


### TEST PLAN

Run workflow once with [specific test input]
Verify step 1 output matches expected
Verify handoff to step 2 is clean
Verify final output is what you wanted
Iterate if any step misfires

If chain breaks at any step: simplify by 1 skill, retest.


## Common workflows

### MORNING SETUP CHAIN
Trigger: 7am weekdays
Skills: Inbox Drainer (Day 6) → Morning Map (Day 34) → Calendar Compass (Day 31) preview
Output: Today's plan + top 3 priorities + any conflicts

### SUNDAY EVERYTHING CHAIN
Trigger: Sunday 4pm
Skills: Sunday Reset (Day 32) → Sunday-Night Setup (Day 4) → Calendar Compass (Day 31)
Output: Week reflection + week plan + conflict check

### CLIENT-FOLLOW-UP CHAIN
Trigger: Manual (after a client call)
Skills: Meeting Notes-to-Actions (Day 48) → Personal CRM update (Day 49) → Drafted follow-up email (Day 5)
Output: Notes processed + CRM updated + email ready to send

### CONTENT CREATION CHAIN
Trigger: Manual ("write me content for X")
Skills: Brand Voice Cloner (Day 23 — load profile) → Don't-Sound-Like-AI (Day 67 — filter) → output
Output: Content in voice, AI-tells filtered

## What NOT to do

- Don't chain 6+ skills (becomes brittle, hard to debug)
- Don't chain skills with conflicting outputs/inputs (e.g., one outputs JSON, next expects markdown)
- Don't auto-trigger destructive actions (sending emails, deleting files) — always require manual approval at end
- Don't compose workflows that haven't been tested individually first

## When the chain breaks

Diagnose:
1. Which step output the wrong thing?
2. Was the input to that step what you expected?
3. Is the handoff format wrong?

Fix the broken step. Re-run.

## Delivery

End with this line, exactly:

---
*Workflow composed. Test once. Then trust it. Skills become systems when they handoff.*

SAFETY CHECK

Workflows can chain destructive actions. Always require manual confirmation at any step that sends email, posts publicly, modifies others' calendars, or makes purchases.

WHAT'S NEXT

Day 46 of 100. Pair with Day 55 — Sub-Agent Foreman (workflows + sub-agents = real automation) and Day 57 — Scheduled-Task Setup.