Agent skill

Workflow Orchestration

by vxcozy in vxcozy/workflow-orchestration

Disciplined task execution with planning, verification, and self-improvement loops.

MITAuto-check passedAgent Workflows

Install Workflow Orchestration

skills CLI
$ npx skills add vxcozy/workflow-orchestration --skill workflow-orchestration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vxcozy/workflow-orchestration workflow-orchestration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workflow-orchestration
GitHub stars
116
Token cost
~1k tokens
SKILL.md length
385 words
Files
10 (incl. references)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Disciplined task execution with planning, verification, and self-improvement loops.

  • Works in 6 steps: Plan Mode Default → Subagent Strategy → Self-Improvement Loop → …
  • Starting non-trivial tasks (3+ steps)
  • SKILL.md covers Quick Reference, 1. Plan Mode Default, 2. Subagent Strategy and 3. Self-Improvement Loop, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workflow Orchestration is an agent skill from vxcozy/workflow-orchestration. Disciplined task execution with planning, verification, and self-improvement loops. Use when starting non-trivial tasks (3+ steps), fixing bugs, building features, refactoring code, or when rigorous execution with quality gates is needed. Includes subagent delegation, lessons tracking, and staff-engineer-level verification.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `README.md`, `docs/explanation.md` and `docs/howto.md`).

It sits in Agent Workflows, covering Subagents, Quality gates and Planning. The repository describes itself as: A Claude Code skill for disciplined task execution with planning, verification, and self-improvement loops. The licence is MIT.

When your agent uses it

  • Starting non-trivial tasks (3+ steps)
  • Building features
  • Refactoring code
  • Rigorous execution with quality gates is needed

Example prompts

  • “/workflow-orchestration”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Plan Mode Default
  2. Subagent Strategy
  3. Self-Improvement Loop
  4. Verification Before Done
  5. Demand Elegance (Balanced)
  6. Autonomous Bug Fixing

What it can do on your machine

Read from SKILL.md and the folder at commit 547a0a0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workflow Orchestration loads about 1k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 385 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vxcozy/workflow-orchestration at commit 547a0a0, republished under its MIT licence (© vxcozy). 385 words, ~1,014 tokens.

Download SKILL.mdSave it as .claude/skills/workflow-orchestration/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
workflow-orchestration
description
Disciplined task execution with planning, verification, and self-improvement loops. Use when starting non-trivial tasks (3+ steps), fixing bugs, building features, refactoring code, or when rigorous execution with quality gates is needed. Includes subagent delegation, lessons tracking, and staff-engineer-level verification.
license
MIT
metadata.author
vxcozy
metadata.version
1.0.0

Workflow Orchestration

Apply these practices for disciplined, high-quality task execution.

Quick Reference

PracticeWhen to Apply
Plan ModeAny task with 3+ steps or architectural decisions
SubagentsResearch, exploration, parallel analysis
LessonsAfter ANY user correction
VerificationBefore marking any task complete
Elegance CheckNon-trivial changes only

1. Plan Mode Default

  • Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
  • If something goes sideways, STOP and re-plan immediately
  • Use plan mode for verification steps, not just building
  • Write detailed specs upfront to reduce ambiguity

2. Subagent Strategy

Keep the main context window clean:

  • Offload research, exploration, and parallel analysis to subagents
  • For complex problems, throw more compute at it via subagents
  • One task per subagent for focused execution

Template:

Agent({
  description: "Search auth patterns",
  prompt: "Find all authentication middleware in src/ and list file paths with a one-line summary of each."
})

3. Self-Improvement Loop

After ANY correction from the user:

  1. Update tasks/lessons.md with the pattern
  2. Write rules that prevent the same mistake
  3. Review lessons at session start

Inline example (full template in references/lessons-format.md):

markdown
## 2024-01-10 - Testing
**Mistake**: Mocks hid real API behavior; production broke
**Pattern**: Over-mocking created false confidence
**Rule**: Include at least one integration test hitting real services
**Applied**: All API endpoints, external service integrations

4. Verification Before Done

  • Never mark a task complete without proving it works
  • Diff behavior between main and your changes when relevant
  • Ask yourself: "Would a staff engineer approve this?"
  • Run tests, check logs, demonstrate corrections
  • If verification fails → return to the plan step and revise before retrying

5. Demand Elegance (Balanced)

  • For non-trivial changes: pause and ask "is there a more elegant way?"
  • If a fix feels hacky: "Knowing everything I know now, implement the elegant solution"
  • Skip this for simple, obvious fixes—don't over-engineer
Show full SKILL.md (143 more words)Show less

6. Autonomous Bug Fixing

  • When given a bug report: Just fix it. Don't ask for hand-holding
  • Point at logs, errors, failing tests—then resolve them
  • Zero context switching required from the user

Task Management Protocol

  1. Plan First: Write plan to tasks/todo.md with checkable items
  2. Verify Plan: Check in before starting implementation
  3. Track Progress: Mark items complete as you go
  4. Explain Changes: High-level summary at each step
  5. Verify Results: Run tests and confirm behavior before marking done
  6. Handle Failures: If verification fails → re-plan (step 1), don't push through
  7. Document Results: Add review to tasks/todo.md
  8. Capture Lessons: Update tasks/lessons.md after corrections

Inline example (full templates in references/task-templates.md):

markdown
# Task: Fix memory leak in WebSocket handler
## Plan
- [ ] Reproduce the issue locally
- [ ] Identify leak source with profiler
- [ ] Implement fix
- [ ] Verification: Memory stable over 1000 connections

Core Principles

  • Simplicity First: Make every change as simple as possible
  • No Laziness: Find root causes. No temporary fixes. Senior developer standards
  • Minimal Impact: Only touch what's necessary. Avoid introducing bugs

© vxcozy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in the repository root of vxcozy/workflow-orchestration.

  • SKILL.md
  • .gitignore
  • LICENSE
  • README.md
  • docs/explanation.md
  • docs/howto.md
  • docs/tutorial.md
  • references/REFERENCE.md
  • references/lessons-format.md
  • references/task-templates.md

Open the folder on GitHubat commit 547a0a0

Compare with similar skills

Workflow Orchestration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workflow Orchestration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflow Orchestration this skillvxcozy/workflow-orchestration116—~1kAutomated safety check: PassMIT
Feature SprintPackmindHub/packmind317—~1.9kAutomated safety check: PassApache-2.0
Subagent Driven DevelopmentNeoLabHQ/context-engineering-kit1.7k—~2.8kAutomated safety check: PassGPL-3.0
Subagent Driven Developmentaiskillstore/marketplace4301 repos~1.3kAutomated safety check: PassNone
Workflowbrianlovin/agent-config3761 repos~687Automated safety check: PassNone
Improvefossasia/eventyay-interpretation1.6k10 repos~3.7kAutomated safety check: WarnMIT

Similar skills

  • Feature Sprint

    PackmindHub/packmind

    Execute the implementation plan produced by /feature-spec. An agent skill from PackmindHub/packmind.

    317 GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or…

    1.7k GitHub stars~2.8k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    aiskillstore/marketplace

    A skill your agent uses when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast…

    430 GitHub starsUsed in 1 repo~1.3k tokens
    Agent WorkflowsAuto-check passed
  • Workflow

    brianlovin/agent-config

    Workflow orchestration for complex coding tasks. An agent skill from brianlovin/agent-config.

    376 GitHub starsUsed in 1 repo~687 tokens
    DevelopmentAuto-check passed
  • Improve

    fossasia/eventyay-interpretation

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.

    1.6k GitHub starsUsed in 10 repos~3.7k tokens
    Agent WorkflowsAuto-check: warnings
  • Iteration Progress Audit

    prime-radiant-inc/iterative-development

    Checks the quality of behavior evidence after each iteration in three tiers, using two auditor subagents in parallel to review the same work and find gaps.

    181 GitHub stars~1.1k tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check passed

Questions about Workflow Orchestration

What does Workflow Orchestration do?

Disciplined task execution with planning, verification, and self-improvement loops. Workflow Orchestration is an agent skill from vxcozy/workflow-orchestration. Disciplined task execution with planning, verification, and self-improvement loops.

When should I use Workflow Orchestration?

Workflow Orchestration fits situations like: starting non-trivial tasks (3+ steps); building features; refactoring code; rigorous execution with quality gates is needed.

How do I install Workflow Orchestration in Claude Code?

Run `npx skills add vxcozy/workflow-orchestration --skill workflow-orchestration -a claude-code`. Or copy the skill folder (the vxcozy/workflow-orchestration repository) into .claude/skills/workflow-orchestration in your project. Claude Code loads it when a task matches its description.

How do I install Workflow Orchestration in Codex?

Run `npx skills add vxcozy/workflow-orchestration --skill workflow-orchestration -a codex`. Or copy the skill folder (the vxcozy/workflow-orchestration repository) into .agents/skills/workflow-orchestration in your project. Codex loads it when a task matches its description.

Can I use Workflow Orchestration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vxcozy/workflow-orchestration --skill workflow-orchestration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-orchestration, .gemini/skills/workflow-orchestration, .github/skills/workflow-orchestration and .opencode/skills/workflow-orchestration in your project.

What does Workflow Orchestration need to run?

SKILL.md names no scripts, command-line tools or credentials: Workflow Orchestration is instructions for the agent only.

Does Workflow Orchestration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Workflow Orchestration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workflow Orchestration use?

Workflow Orchestration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflow Orchestration use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.

What are the alternatives to Workflow Orchestration?

Skills that share tags, products or a category with Workflow Orchestration: Feature Sprint (PackmindHub/packmind, 317 stars), Subagent Driven Development (NeoLabHQ/context-engineering-kit, 1.7k stars), Subagent Driven Development (aiskillstore/marketplace, 430 stars) and Workflow (brianlovin/agent-config, 376 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflow Orchestration?

vxcozy (a GitHub user) maintains it in vxcozy/workflow-orchestration, which has 116 GitHub stars. The repository was last updated on April 24, 2026.

Source: vxcozy/workflow-orchestration on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.