
Workflow Orchestrator
- 753 installs
- 65 repo stars
- Updated June 21, 2026
- charon-fan/agent-playbook
Workflow Orchestrator is a Claude Code skill that automatically chains multiple skills together and triggers follow-up actions when a milestone completes for developers who run multi-step agent workflows.
About
Workflow Orchestrator is a Claude Code skill from charon-fan/agent-playbook that coordinates multi-skill workflows using hook definitions. It reads hook definitions from skills/auto-trigger/SKILL.md and executes follow-up actions based on auto, background, or ask_first modes while logging progress and context to session-logger. Developers invoke it with phrases like Complete workflow or Finish the process and trigger next steps after milestones such as PRD creation or implementation. Workflow Orchestrator removes manual skill handoffs when an agent playbook defines sequential or conditional next actions. It fits teams building repeatable agent pipelines where one completed task should reliably launch the next skill without re-prompting.
- Reads hook definitions from skills/auto-trigger/SKILL.md
- Supports auto, background, and ask_first trigger modes
- Automatically coordinates multi-skill workflows at milestones
- Logs progress and context via session-logger after every completion
- Activates on phrases like "complete workflow" or "finish the process"
Workflow Orchestrator by the numbers
- 753 all-time installs (skills.sh)
- Ranked #343 of 2,742 Automation & Workflows skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/charon-fan/agent-playbook --skill workflow-orchestratorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 753 |
|---|---|
| repo stars | ★ 65 |
| Security audit | 2 / 3 scanners passed |
| Last updated | June 21, 2026 |
| Repository | charon-fan/agent-playbook ↗ |
How do you chain Claude Code skills automatically?
Automatically chain multiple skills together and trigger follow-up actions when a milestone completes.
Who is it for?
Developers running agent-playbook workflows who need automatic skill handoffs after PRD creation, implementation, or other defined milestones.
Skip if: Single-skill tasks with no hook definitions or developers who want manual control over every follow-up action without orchestration.
When should I use this skill?
A milestone completes and the developer says Complete workflow, Finish the process and trigger next steps, or any task requiring chained skill execution.
What you get
Executed follow-up skill actions, session-logger progress entries, and completed multi-skill workflow chains.
- Chained skill executions
- Session-logger workflow entries
Files
Workflow Orchestrator
A skill that coordinates workflows across multiple skills by evaluating hook metadata, recording pending follow-ups, and running only the actions that are safe and supported in the current host runtime.
When This Skill Activates
This skill should be used when:
- A skill completes its main workflow
- A milestone is reached (PRD complete, implementation done, etc.)
- User says "complete workflow" or "finish the process"
How It Works
┌─────────────────────────────────────────────────────────────┐
│ Workflow Orchestration │
├─────────────────────────────────────────────────────────────┤
│ │
│ 1. Detect Milestone → 2. Read Hooks → 3. Record/Run Safe Follow-ups │
│ │
│ prd-planner complete │
│ ↓ │
│ workflow-orchestrator │
│ ↓ │
│ ┌─────────────────────────────────────┐ │
│ │ auto-trigger self-improving-agent │ (background) │
│ │ auto-trigger session-logger │ (auto) │
│ └─────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘Trigger Configuration
Read trigger definitions from skills/auto-trigger/SKILL.md:
hooks:
after_complete:
- trigger: self-improving-agent
mode: background
- trigger: session-logger
mode: auto
on_error:
- trigger: self-improving-agent
mode: backgroundExecution Modes
| Mode | Behavior | Use When |
|---|---|---|
auto | Run or record a low-risk follow-up when the host supports it | Logging, status updates |
background | Record a non-blocking follow-up | Reflection, analysis |
ask_first | Ask user before executing | PRs, deployments, major changes |
Milestone Detection
PRD Complete
Detected when:
- docs/{scope}-prd.md exists
- All phases in {scope}-prd-task-plan.md are checked
- Status shows "COMPLETE"
Actions:
1. Record self-improving-agent as a background follow-up
2. Run or record session-logger if the host supports itImplementation Complete
Detected when:
- All PRD requirements implemented
- Tests pass
- Code committed
Actions:
1. Ask before running code-reviewer
2. Run create-pr only when the user requested submission
3. Run or record session-logger if the host supports itSelf-Improvement Complete
Detected when:
- Reflection complete
- Patterns abstracted
- Skill files modified
Actions:
1. Ask before running create-pr
2. Run or record session-logger if the host supports itLearning Candidate (Skill Complete)
Detected when:
- A skill completes its workflow and produces reusable evidence
- User provides feedback
- Error or issue encountered
Actions:
1. Record self-improving-agent as a background follow-up
2. Run or record session-logger if the host supports it
The self-improving-agent:
- Extracts experience from completed skill
- Identifies patterns and insights
- Writes memory or proposal artifacts
- Promotes validated changes only after explicit approval or strong evidence
- Consolidates memory for future referenceError Handling (on_error)
Detected when:
- A command returns non-zero exit code
- Tests fail after following skill guidance
- User reports the guidance produced incorrect results
Actions: 1. Record self-improving-agent (background) for self-correction 2. Run or record session-logger to capture error context
Hook Implementation in Skills
To declare follow-up metadata, add this section to any skill's SKILL.md:
## Auto-Trigger (After Completion)
When this skill completes, record or run supported follow-ups:
hooks: after_complete:
- trigger: skill-name
mode: auto|background|ask_first context: "relevant context" on_error:
- trigger: self-improving-agent
mode: background
### Current Skill Hooks
- **prd-planner**: After PRD complete → self-improving-agent + session-logger
- **self-improving-agent**: After improvement → create-pr + session-logger
- **prd-implementation-precheck**: After implementation → self-improving-agent + session-logger
- **code-reviewer**: After review → self-improving-agent + session-logger
- **debugger**: After debugging → self-improving-agent + session-logger
- **create-pr**: After PR created → session-logger
- **session-logger**: No trigger (terminates chain)
### Universal Learning Pattern
┌─────────────────────────────────────────────────────────────┐ │ Skill Completes With Evidence │ └──────────────┬──────────────────────────────────────────────┘ │ ↓ ┌──────────────────────┐ │ workflow-orchestrator │ └──────────┬───────────┘ │ ┌──────────┴─────────┐ ↓ ↓ self-improving-agent session-logger ↓ ↓ Capture proposal Save context ↓ ↓ Validate changes Log session ↓ create-pr (if modified)
Workflow Examples
Example 1: PRD Creation Workflow
User: "Create a PRD for user authentication"
↓
prd-planner executes
↓
Phase 6 complete: PRD delivered
↓
workflow-orchestrator detects milestone
↓
┌─────────────────────────────────┐
│ Background: self-improving-agent │ → Records learning proposal
│ Auto: session-logger │ → Saves session when supported
└─────────────────────────────────┘Example 2: Full Feature Workflow
User: "Create a PRD and implement it"
↓
prd-planner → workflow-orchestrator
↓
self-improving-agent → workflow-orchestrator
↓
prd-implementation-precheck
↓
implementation complete → workflow-orchestrator
↓
code-reviewer → self-improving-agent → workflow-orchestrator
↓
create-pr → workflow-orchestrator
↓
session-loggerEach milestone can produce a self-improving-agent follow-up, but durable skill edits still require validation or explicit approval.
Implementation Steps
Step 1: Detect Milestone
Check for completion indicators:
# PRD complete?
grep -q "COMPLETE" docs/{scope}-prd-task-plan.md
# All phases checked?
grep -q "^\- \[x\].*Phase 6" docs/{scope}-prd-task-plan.md
# PRD file exists?
ls docs/{scope}-prd.mdStep 2: Read Trigger Config
# Read hooks from auto-trigger skill
cat skills/auto-trigger/SKILL.mdStep 3: Record or Execute Hooks
For each hook in order (before_start, after_complete, on_error): 1. Check if condition is met 2. Record or execute based on mode and host support 3. Pass context to triggered skill 4. Wait/continue based on mode
Step 4: Update Status
Log what was triggered and the result:
## Workflow Execution
- [x] self-improving-agent (background) - Started
- [x] session-logger (auto) - Session saved
- [ ] create-pr (ask_first) - Pending user approvalSkills with Auto-Trigger
| Skill | Triggers After |
|---|---|
prd-planner | self-improving-agent, session-logger |
self-improving-agent | create-pr, session-logger |
prd-implementation-precheck | self-improving-agent, session-logger |
code-reviewer | self-improving-agent, session-logger |
create-pr | session-logger |
refactoring-specialist | self-improving-agent, session-logger |
debugger | self-improving-agent, session-logger |
Adding Follow-up Metadata to Existing Skills
To add follow-up metadata to an existing skill, add to the end of its SKILL.md:
---
## Auto-Trigger
When this skill completes, record or run supported follow-ups:
hooks: after_complete:
- trigger: session-logger
mode: auto context: "Save session context"
For more complex triggers, specify mode and context:
## Auto-Trigger
When this skill completes:
hooks: after_complete:
- trigger: next-skill
mode: background context: "Description"
- trigger: session-logger
mode: auto context: "Save session"
- trigger: create-pr
mode: ask_first context: "Create PR if files modified" on_error:
- trigger: self-improving-agent
mode: background
Best Practices
1. Always log to session - Every workflow should end with session-logger 2. Ask before major actions - PRs, deployments, destructive changes 3. Background for analysis - Reflection, evaluation, optimization 4. Auto for status - Logging, status updates, bookmarks 5. Don't create loops - Ensure chains terminate
Workflow Orchestrator
A skill that coordinates multi-skill workflows using hook definitions.
Installation
This skill is part of the agent-playbook collection.
Usage
You: Complete workflow
You: Finish the process and trigger next stepsHow It Works
- Reads hook definitions from
skills/auto-trigger/SKILL.md - Records or runs supported follow-up actions based on
auto,background, orask_firstmodes - Logs progress and context to
session-logger
Related skills
How it compares
Pick Workflow Orchestrator when agent-playbook hook definitions already exist and milestones need automatic skill handoffs rather than ad-hoc single-skill prompts.
FAQ
How does Workflow Orchestrator chain skills?
Workflow Orchestrator reads hook definitions from skills/auto-trigger/SKILL.md and executes follow-up actions when a milestone completes. Modes include auto, background, and ask_first, and progress is logged to session-logger for traceability across the workflow.
When should developers invoke Workflow Orchestrator?
Developers should invoke Workflow Orchestrator after PRD creation, implementation, or any milestone that should trigger the next skill automatically. Phrases like Complete workflow or Finish the process and trigger next steps activate the orchestration.
Is Workflow Orchestrator safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.