delegated-execution
From the author
Use when a written implementation plan is ready to execute in the current session and its tasks are mostly independent, so each one can go to a fresh implementer subagent with its own review.
Install
npx skills add NoobyGains/godmode --skill delegated-execution -a claude-code
Installs to .claude/skills/delegated-execution/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- executing-plansGanyuanRan/AegisUse when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-development instead.Planning★ 1.4K
- implementation-planningcbrock84/headcountTurns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.Planning★ 2.6K
- subagent-driven-developmentforyourhealth111-pixel/Vibe-SkillsUse when executing implementation plans with independent tasks in the current sessionPlanning★ 3.8K
- inline-executionNoobyGains/godmodeUse when a written implementation plan is to be executed by the current agent itself rather than by subagents: the user chose the cheaper mode, the harness cannot dispatch subagents, or the plan is short and fully specified.Writing★ 115
- plan-executionthiientv/godmodeExecutes an existing implementation plan task by task, preserving its interfaces and constraints, running focused checks after each slice, and stopping when the repository differs from the plan. Use when a written plan or approved checklist already exists. Not for inventing the plan, debugging an unexplained failure, or broad unscoped cleanup.Planning★ 99
- pitroom-driven-developmentATASTECH/pitroomUse when executing a written implementation plan - each task goes to a Pitroom worker in an isolated copy, a worker on another model reviews it, and you rule, apply and commit between tasks.Writing★ 51
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in