wf-composer
Skill2.1k starsChanged 7 months agoMITArchived repositoryView on GitHub
Semantic workflow composer — parse natural language workflow description into a DAG of skill/CLI/agent nodes, auto-inject checkpoint save nodes, confirm with user, persist as reusable JSON template. Triggers on "wf-composer " or "/wf-composer".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- zhao-wuyan/ccw-command-explorerword for word, first seen May 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- zhao-wuyan/ccw-command-explorer★ 45100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository59 other files it gives its agents.
- .codex/AGENTS.mdAGENTS.md
- brainstormSkill
- ccw-chainSkill
- ccw-helpSkill
- delegation-checkSkill
- investigateSkill
- issue-manageSkill
- memory-captureSkill
- memory-manageSkill
- prompt-generatorSkill
- review-codeSkill
- review-cycleSkill
- security-auditSkill
- shipSkill
- skill-generatorSkill
- skill-iter-tuneSkill
- skill-simplifySkill
- skill-tuningSkill
- spec-generatorSkill
- team-arch-optSkill
- team-brainstormSkill
- team-coordinateSkill
- team-designerSkill
- team-executorSkill
- team-frontend-debugSkill
- team-frontendSkill
- team-interactive-craftSkill
- team-issueSkill
- team-lifecycle-v4Skill
- team-motion-designSkill
- team-perf-optSkill
- team-planexSkill
- team-quality-assuranceSkill
- team-reviewSkill
- team-roadmap-devSkill
- team-tech-debtSkill
- team-testingSkill
- team-uidesignSkill
- team-ui-polishSkill
- team-ultra-analyzeSkill
- team-ux-improveSkill
- team-visual-a11ySkill
- wf-playerSkill
- workflow-executeSkill
- workflow-lite-executeSkill
- workflow-lite-planSkill
- workflow-lite-test-reviewSkill
- workflow-multi-cli-planSkill
- workflow-planSkill
- workflow-skill-designerSkill
- workflow-tdd-plan-planSkill
- workflow-test-fixSkill
- brainstormSkill
- investigateSkill
- review-cycleSkill
- spec-generatorSkill
- workflow-planSkill
- workflow-tdd-planSkill
- workflow-test-fixSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 60
Read phases/01-parse.md and execute.
- Very specific: line 92
After every skill → skill transition that crosses a semantic phase boundary
- Very specific: line 93
Before any long-running agent spawn
- Distinctive: line 94
After any node that produces a persistent artifact (plan, spec, analysis)
- Distinctive: line 126
Add node after (select position)
- Distinctive: line 127
Remove node (select node ID)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Workflow Design
Parse user's semantic workflow description → decompose into nodes → map to executors → auto-inject checkpoints → confirm pipeline → save as reusable workflow-template.json.
Architecture
User describes workflow in natural language
-> Phase 1: Parse — extract intent steps + variables
-> Phase 2: Resolve — map each step to executor (skill/cli/agent/command)
-> Phase 3: Enrich — inject checkpoint nodes, set DAG edges
-> Phase 4: Confirm — visualize pipeline, user approval/edit
-> Phase 5: Persist — save .workflow/templates/<name>.jsonShared Constants
| Constant | Value |
| Session prefix | WFD |
| Template dir | .workflow/templates/ |
| Template ID format | wft-<slug>-<date> |
| Node ID format | N-<seq> (e.g. N-001), CP-<seq> for checkpoints |
| Max nodes | 20 |
Entry Router
Parse $ARGUMENTS.
| Detection | Condition | Handler |
| Resume design | --resume flag or existing WFD session | -> Phase 0: Resume |
| Edit template | --edit <template-id> flag | -> Phase 0: Load + Edit |
| New design | Default | -> Phase 1: Parse |
Phase 0: Resume / Edit (optional)
Resume design session:
- Scan
.workflow/templates/design-drafts/WFD-*.jsonfor in-progress designs - Multiple found → AskUserQuestion for selection
- Load draft → skip to last incomplete phase
Edit existing template:
- Load template from
--editpath - Show current pipeline visualization
- AskUserQuestion: which nodes to modify/add/remove
- Re-enter at Phase 3 (Enrich) with edits applied
Phase 1: Parse
Read phases/01-parse.md and execute.
Objective: Extract structured semantic steps + context variables from natural language.
Success: design-session/intent.json written with: steps[], variables[], task_type, complexity.
Phase 2: Resolve
Read phases/02-resolve.md and execute.
Objective: Map each intent step to a concrete executor node.
Executor types:
skill— invoke viaSkill(skill=..., args=...)cli— invoke viaccw cli -p "..." --tool ... --mode ...command— invoke viaSkill(skill="<namespace:command>", args=...)agent— invoke viaAgent(subagent_type=..., prompt=...)checkpoint— state save + optional user pause
Success: design-session/nodes.json written with resolved executor for each step.
Phase 3: Enrich
Read phases/03-enrich.md and execute.
Objective: Build DAG edges, auto-inject checkpoints at phase boundaries, validate port compatibility.
Checkpoint injection rules:
- After every
skill→skilltransition that crosses a semantic phase boundary - Before any long-running
agentspawn - After any node that produces a persistent artifact (plan, spec, analysis)
- At user-defined breakpoints (if any)
Success: design-session/dag.json with nodes[], edges[], checkpoints[], context_schema{}.
Phase 4: Confirm
Read phases/04-confirm.md and execute.
Objective: Visualize the pipeline, present to user, incorporate edits.
Display format:
Pipeline: <template-name>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
N-001 [skill] workflow-lite-plan "{goal}"
|
CP-01 [checkpoint] After Plan auto-continue
|
N-002 [skill] workflow-test-fix "--session N-001"
|
CP-02 [checkpoint] After Tests pause-for-user
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Variables: goal (required)
Checkpoints: 2 (1 auto, 1 pause)AskUserQuestion:
- Confirm & Save
- Edit node (select node ID)
- Add node after (select position)
- Remove node (select node ID)
- Rename template
Success: User confirmed pipeline. Final dag.json ready.
Phase 5: Persist
Read phases/05-persist.md and execute.
Objective: Assemble final template JSON, write to template library, output summary.
Output:
.workflow/templates/<slug>.json— the reusable template- Console summary with template path + usage command
Success: Template saved. User shown: Skill(skill="wf-player", args="<template-path>")
Specs Reference
| Spec | Purpose |
| specs/node-catalog.md | Available executors, port definitions, arg templates |
| specs/template-schema.md | Full JSON template schema |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

