A skill that automatically coordinates workflows across multiple skills, triggering follow-up actions at appropriate milestones.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionworkflow-orchestratorExecute the skills CLI command in your project's root directory to begin installation:
Fetches workflow-orchestrator from charon-fan/agent-playbook and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate workflow-orchestrator. Access via /workflow-orchestrator in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
27
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
27
stars
A skill that automatically coordinates workflows across multiple skills, triggering follow-up actions at appropriate milestones.
This skill should be triggered automatically when:
┌─────────────────────────────────────────────────────────────┐
│ Workflow Orchestration │
├─────────────────────────────────────────────────────────────┤
│ │
│ 1. Detect Milestone → 2. Read Hooks → 3. Execute Chain │
│ │
│ prd-planner complete │
│ ↓ │
│ workflow-orchestrator │
│ ↓ │
│ ┌─────────────────────────────────────┐ │
│ │ auto-trigger self-improving-agent │ (background) │
│ │ auto-trigger session-logger │ (auto) │
│ └─────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘
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: background
| Mode | Behavior | Use When |
|---|---|---|
auto |
Execute immediately, no confirmation | Logging, status updates |
background |
Execute without blocking | Reflection, analysis |
ask_first |
Ask user before executing | PRs, deployments, major changes |
Detected when:
- docs/{scope}-prd.md exists
- All phases in {scope}-prd-task-plan.md are checked
- Status shows "COMPLETE"
Actions:
1. Trigger self-improving-agent (background)
2. Trigger session-logger (auto)
Detected when:
- All PRD requirements implemented
- Tests pass
- Code committed
Actions:
1. Trigger code-reviewer (ask_first)
2. Trigger create-pr if changes staged
3. Trigger session-logger (auto)
Detected when:
- Reflection complete
- Patterns abstracted
- Skill files modified
Actions:
1. Trigger create-pr (ask_first)
2. Trigger session-logger (auto)
Detected when:
- ANY skill completes its workflow
- User provides feedback
- Error or issue encountered
Actions:
1. Trigger self-improving-agent (background)
2. Trigger session-logger (auto)
The self-improving-agent:
- Extracts experience from completed skill
- Identifies patterns and insights
- Updates related skills with learned patterns
- Consolidates memory for future reference
Detected when:
Actions:
To enable auto-trigger, add this section to any skill's SKILL.md:
## Auto-Trigger (After Completion)
When this skill completes, automatically trigger:
```yaml
hooks:
after_complete:
- trigger: skill-name
mode: auto|background|ask_first
context: "relevant context"
on_error:
- trigger: self-improving-agent
mode: background
┌─────────────────────────────────────────────────────────────┐
│ ANY Skill Completes │
└──────────────┬──────────────────────────────────────────────┘
│
↓
┌──────────────────────┐
│ workflow-orchestrator │
└──────────┬───────────┘
│
┌──────────┴─────────┐
↓ ↓
self-improving-agent session-logger
↓ ↓
Learn from experience Save context
↓ ↓
Update skills 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 │ → Learns from PRD patterns │ Auto: session-logger │ → Saves session └─────────────────────────────────┘
### 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-logger
Each step triggers `self-improving-agent` to learn from the experience.
## Implementation Steps
### Step 1: Detect Milestone
Check for completion indicators:
```bash
# 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.md
# Read hooks from auto-trigger skill
cat skills/auto-trigger/SKILL.md
For each hook in order (before_start, after_complete, on_error):
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 approval
| Skill | Triggers After |
|---|---|
prd-planner |
self-improving-agent, session-logger |
self-improving-agent |
create-pr, session-logger |
prd-implementation-precheck |
code-reviewer, 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 |
To add auto-trigger capability to an existing skill, add to the end of its SKILL.md:
---
## Auto-Trigger
When this skill completes, automatically trigger:
```yaml
hooks:
after_complete:
- trigger: session-logger
mode: auto
context: "Save session context"
For more complex triggers, specify mode and context:
```markdown
## Auto-Trigger
When this skill completes:
```yaml
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
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Solid pick for teams standardizing on skills: workflow-orchestrator is focused, and the summary matches what you get after install.
workflow-orchestrator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
workflow-orchestrator reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: workflow-orchestrator is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added workflow-orchestrator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added workflow-orchestrator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: workflow-orchestrator is focused, and the summary matches what you get after install.
I recommend workflow-orchestrator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
workflow-orchestrator has been reliable in day-to-day use. Documentation quality is above average for community skills.
workflow-orchestrator has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 43