Agent skill

Task Execution Workflow

by Yeachan-Heo in Yeachan-Heo/oh-my-claudecode

Takes an agreed task from intent to working code: splits it into units, implements the smallest correct change, verifies as it goes and reports what is left.

MITAuto-check passedAgent Workflows

Install Task Execution Workflow

skills CLI
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill execute -a claude-code

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

GitHub CLI
$ gh skill install Yeachan-Heo/oh-my-claudecode execute --agent claude-code

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

Manual copy
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/execute .claude/skills/execute && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

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

Facts

Skill name
execute
GitHub stars
40k
Token cost
~431 tokens
SKILL.md length
241 words
Files
1
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

Takes an agreed task from intent to working code: splits it into units, implements the smallest correct change, verifies as it goes and reports what is left.

  • Works in 5 steps: Confirm the task is clear enough to… → Break the work into independent units;… → Implement the smallest correct change… → …
  • Building a task whose scope and approach have already been agreed
  • SKILL.md covers Goal, Workflow, Scale and Rules, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This is the main build workflow for work that is already understood. The agent first confirms the task is clear enough to build, and plans if it is not. It then splits the job into independent units, runs the genuinely independent ones in parallel, implements the smallest correct change per unit with existing utilities, verifies along the way and reports what changed, what was verified and what remains. Workflows named autopilot, ralph, ultragoal, ultrapilot, pipeline and swarm route to it.

The machinery scales with the task: a single unit is done directly, several independent units go to executor agents in parallel, long-running work keeps a durable task list until it is empty, and coordinated parallel workers use team. Rules include preferring deletion when behavior is preserved, adding no dependencies unprompted, keeping diffs small and treating placeholder TODOs, test.skip and stub tests as blockers. Authoring and approval stay separate, so finished work is handed to review or verify rather than self-approved.

When your agent uses it

  • Building a task whose scope and approach have already been agreed
  • Splitting a build into independent units that can run in parallel
  • Getting a final report of files changed, evidence and open items

Example prompts

  • “The plan for the export feature is approved, so implement it and show me the test evidence.”
  • “Carry out the agreed refactor of the auth middleware and report anything still open.”
  • “Work through the approved task list for the settings page until every item is done.”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the task is clear enough to build. If it is not, plan first.
  2. Break the work into independent units; run genuinely independent units in parallel.
  3. Implement the smallest correct change per unit, reusing existing utilities and patterns.
  4. Verify as you go, not only at the end.
  5. Report what changed, what was verified, and what remains.

What it can do on your machine

Read from SKILL.md and the folder at commit 454bae0. 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.

    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

Task Execution Workflow loads about 431 tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 241 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~16
When it runs · the whole SKILL.md, loaded when a task matches
~431

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 Yeachan-Heo/oh-my-claudecode at commit 454bae0, republished under its MIT licence (© Yeachan-Heo). 241 words, ~431 tokens.

Download SKILL.mdSave it as .claude/skills/execute/SKILL.md (or your agent's skills folder).
name
execute
description
Carry an approved task through to working, verified code

Execute

Use this skill when the work is understood and the job is to build it.

This is the canonical execution workflow. autopilot, ralph, ultragoal, ultrapilot, pipeline, and swarm route here.

Goal

Take a task from agreed intent to working code, with evidence that it works.

Workflow

  1. Confirm the task is clear enough to build. If it is not, plan first.
  2. Break the work into independent units; run genuinely independent units in parallel.
  3. Implement the smallest correct change per unit, reusing existing utilities and patterns.
  4. Verify as you go, not only at the end.
  5. Report what changed, what was verified, and what remains.

Scale

Match the machinery to the task:

  • Single unit — implement directly, verify, done.
  • Several independent units — delegate to executor agents in parallel.
  • Long-running or unbounded — keep a durable task list and continue until the list is empty.
  • Needs coordinated parallel workers — use team.

Do not spin up coordination for work that one focused pass would finish.

Rules

  • Prefer deletion over addition when behavior is preserved.
  • Do not add dependencies without an explicit request.
  • Keep diffs small and reversible.
  • Placeholder TODOs, test.skip, and stub tests are blockers, not progress.
  • Authoring and approval are separate passes — do not self-approve; hand off to review or verify.

Completion

Before claiming done:

  • No pending tasks
  • Tests pass, or failures are reported plainly
  • Verification evidence collected

Output

  • Files changed
  • What was implemented
  • Evidence it works
  • What is still open

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

Files

Just SKILL.md in skills/execute of Yeachan-Heo/oh-my-claudecode.

Open the folder on GitHubat commit 454bae0

Compare with similar skills

Task Execution Workflow 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.

Task Execution Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Task Execution Workflow this skillYeachan-Heo/oh-my-claudecode40k—~431Automated safety check: PassMIT
Incremental Implementationaddyosmani/agent-skills102k1 repos~2.3kAutomated safety check: PassMIT
Vspawnvlinx-io/VelaTerm259—~2.5kAutomated safety check: PassMIT
Auditable Playbook Designercursor/plugins10k8 repos~1kAutomated safety check: PassNone
Cline Pilotsickn33/agentic-awesome-skills47k1 repos~4.6kAutomated safety check: PassMIT
Team Agent Pipelinezereight/gitlab-mcp2k1 repos~1.5kAutomated safety check: PassMIT

Similar skills

  • Incremental Implementation

    addyosmani/agent-skills

    Delivers a change in thin vertical slices, each implemented, tested, verified and committed before the next, using vertical, contract-first or risk-first slicing.

    102k GitHub starsUsed in 1 repo~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Vspawn

    vlinx-io/VelaTerm

    Explicitly spawn a standalone child session under the current vlx-term session, passing the task in as its first message (mirrors spawntask).

    259 GitHub stars~2.5k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Official

    Designs a step-by-step playbook for large or unfamiliar work, runs it as a loop of hypotheses and measurements, and logs decisions so a human can review them later.

    10k GitHub starsUsed in 8 repos~1k tokens
    Agent WorkflowsAuto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Agent WorkflowsAuto-check passed
  • Team Agent Pipeline

    zereight/gitlab-mcp

    Spawns a chosen number of coordinated agents on a shared task list and runs them through plan, requirements, execution, verification and fix stages.

    2k GitHub starsUsed in 1 repo~1.5k tokens
    Agent WorkflowsAuto-check passed
  • Plan Execution Workflow

    EveryInc/compound-engineering-plugin

    Carries out a plan, spec or clear build request end to end with local verification, then hands off to shipping or returns a structured result to a caller.

    25k GitHub stars~2k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from Yeachan-Heo/oh-my-claudecode

All 47 skills in this repo
  • Autopilot

    Yeachan-Heo/oh-my-claudecode

    Takes a short product idea through requirements, design, planning, parallel implementation, QA cycles and multi-reviewer validation to produce working code.

    40k GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check passed
  • Ask Advisor Routing

    Yeachan-Heo/oh-my-claudecode

    Sends a question or task to another locally installed agent CLI, such as Codex or Gemini, through omc ask and saves the answer as a file.

    40k GitHub stars~572 tokensUpdated today
    Auto-check passed
  • Self-Improve Evolutionary Loop

    Yeachan-Heo/oh-my-claudecode

    Runs an autonomous improvement loop on a repository: agents propose and execute plans, a tournament picks the winner by benchmark, and each round is recorded and plotted.

    40k GitHub stars~5.3k tokensUpdated today
    Auto-check: warnings
  • Ask Navigator

    Yeachan-Heo/oh-my-claudecode

    Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.

    40k GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • OMC Mode Cancellation

    Yeachan-Heo/oh-my-claudecode

    Detects and gracefully cancels whichever OMC mode, autopilot, ralph, swarm, pipeline, or team, is currently active, then clears its state.

    40k GitHub stars~4.6k tokensUpdated today
    Auto-check passed
  • Hierarchical AGENTS.md Generator

    Yeachan-Heo/oh-my-claudecode

    Maps a codebase directory by directory and writes linked AGENTS.md files, each pointing to its parent, to document what each area contains.

    40k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Questions about Task Execution Workflow

What does Task Execution Workflow do?

Takes an agreed task from intent to working code: splits it into units, implements the smallest correct change, verifies as it goes and reports what is left. This is the main build workflow for work that is already understood. The agent first confirms the task is clear enough to build, and plans if it is not.

When should I use Task Execution Workflow?

Task Execution Workflow fits situations like: building a task whose scope and approach have already been agreed; splitting a build into independent units that can run in parallel; getting a final report of files changed, evidence and open items.

How do I install Task Execution Workflow in Claude Code?

Run `npx skills add Yeachan-Heo/oh-my-claudecode --skill execute -a claude-code`. Or copy the skill folder (skills/execute in Yeachan-Heo/oh-my-claudecode) into .claude/skills/execute in your project. Claude Code loads it when a task matches its description.

How do I install Task Execution Workflow in Codex?

Run `npx skills add Yeachan-Heo/oh-my-claudecode --skill execute -a codex`. Or copy the skill folder (skills/execute in Yeachan-Heo/oh-my-claudecode) into .agents/skills/execute in your project. Codex loads it when a task matches its description.

Can I use Task Execution Workflow 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 Yeachan-Heo/oh-my-claudecode --skill execute -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/execute, .gemini/skills/execute, .github/skills/execute and .opencode/skills/execute in your project.

What does Task Execution Workflow need to run?

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

Does Task Execution Workflow 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 Task Execution Workflow 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 Task Execution Workflow use?

Task Execution Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Task Execution Workflow use?

About 431 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Task Execution Workflow?

Skills that share tags, products or a category with Task Execution Workflow: Incremental Implementation (addyosmani/agent-skills, 102k stars), Vspawn (vlinx-io/VelaTerm, 259 stars), Auditable Playbook Designer (cursor/plugins, 10k stars) and Cline Pilot (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Task Execution Workflow?

Yeachan-Heo (a GitHub user) maintains it in Yeachan-Heo/oh-my-claudecode, which has 39,638 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 7, 2026.

Source: Yeachan-Heo/oh-my-claudecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.