بنقرة واحدة
delegated-execution
Use when executing implementation plans with independent tasks in the current session
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when executing implementation plans with independent tasks in the current session
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when starting any conversation - establishes how to locate and invoke skills, mandating Skill tool usage before ANY response including clarifying questions
Use when building ANY website, web app, landing page, or web-based UI - searches real template marketplaces for professionally designed layouts in the user's industry or niche, then extracts layout structure, color palettes, typography choices, and section sequences as the design blueprint instead of generating from assumptions
Use when about to build any feature, library, or system - searches GitHub and package registries for existing implementations to study, harvest patterns from, or use directly instead of building from scratch
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Use when making technology, hosting, or infrastructure decisions — recommends services, databases, and deployment strategies based on project requirements and what the user actually has available
Use when starting a session, running shell commands, installing packages, or diagnosing platform-specific failures - detects OS, shell, runtime, package manager, and toolchain before any command execution
| name | delegated-execution |
| description | Use when executing implementation plans with independent tasks in the current session |
Execute a plan by dispatching a fresh subagent per task, with two-stage review after each: specification compliance first, then code quality.
Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
digraph applicability {
"Implementation plan exists?" [shape=diamond];
"Tasks mostly independent?" [shape=diamond];
"Stay in current session?" [shape=diamond];
"delegated-execution" [shape=box];
"task-runner" [shape=box];
"Manual execution or go back to intent-discovery" [shape=box];
"Implementation plan exists?" -> "Tasks mostly independent?" [label="yes"];
"Implementation plan exists?" -> "Manual execution or go back to intent-discovery" [label="no"];
"Tasks mostly independent?" -> "Stay in current session?" [label="yes"];
"Tasks mostly independent?" -> "Manual execution or go back to intent-discovery" [label="no - tightly coupled"];
"Stay in current session?" -> "delegated-execution" [label="yes"];
"Stay in current session?" -> "task-runner" [label="no - separate session"];
}
vs. Task Runner (separate session):
digraph workflow {
rankdir=TB;
subgraph cluster_per_task {
label="Per Task";
"Dispatch builder subagent (./implementer-prompt.md)" [shape=box];
"Builder subagent has questions?" [shape=diamond];
"Answer questions, supply context" [shape=box];
"Builder subagent implements, tests, commits, self-reviews" [shape=box];
"Dispatch spec auditor subagent (./spec-reviewer-prompt.md)" [shape=box];
"Spec auditor confirms code matches spec?" [shape=diamond];
"Builder subagent fixes spec gaps" [shape=box];
"Dispatch quality auditor subagent (./code-quality-reviewer-prompt.md)" [shape=box];
"Quality auditor approves?" [shape=diamond];
"Builder subagent fixes quality issues" [shape=box];
"Mark task complete in plan checklist" [shape=box];
}
"Read plan, extract all tasks with full text, note context, build task checklist" [shape=box];
"More tasks remaining?" [shape=diamond];
"Dispatch final quality auditor for entire implementation" [shape=box];
"Use godmode:merge-protocol" [shape=box style=filled fillcolor=lightgreen];
"Read plan, extract all tasks with full text, note context, build task checklist" -> "Dispatch builder subagent (./implementer-prompt.md)";
"Dispatch builder subagent (./implementer-prompt.md)" -> "Builder subagent has questions?";
"Builder subagent has questions?" -> "Answer questions, supply context" [label="yes"];
"Answer questions, supply context" -> "Dispatch builder subagent (./implementer-prompt.md)";
"Builder subagent has questions?" -> "Builder subagent implements, tests, commits, self-reviews" [label="no"];
"Builder subagent implements, tests, commits, self-reviews" -> "Dispatch spec auditor subagent (./spec-reviewer-prompt.md)";
"Dispatch spec auditor subagent (./spec-reviewer-prompt.md)" -> "Spec auditor confirms code matches spec?";
"Spec auditor confirms code matches spec?" -> "Builder subagent fixes spec gaps" [label="no"];
"Builder subagent fixes spec gaps" -> "Dispatch spec auditor subagent (./spec-reviewer-prompt.md)" [label="re-audit"];
"Spec auditor confirms code matches spec?" -> "Dispatch quality auditor subagent (./code-quality-reviewer-prompt.md)" [label="yes"];
"Dispatch quality auditor subagent (./code-quality-reviewer-prompt.md)" -> "Quality auditor approves?";
"Quality auditor approves?" -> "Builder subagent fixes quality issues" [label="no"];
"Builder subagent fixes quality issues" -> "Dispatch quality auditor subagent (./code-quality-reviewer-prompt.md)" [label="re-audit"];
"Quality auditor approves?" -> "Mark task complete in plan checklist" [label="yes"];
"Mark task complete in plan checklist" -> "More tasks remaining?";
"More tasks remaining?" -> "Dispatch builder subagent (./implementer-prompt.md)" [label="yes"];
"More tasks remaining?" -> "Dispatch final quality auditor for entire implementation" [label="no"];
"Dispatch final quality auditor for entire implementation" -> "Use godmode:merge-protocol";
}
./implementer-prompt.md - Dispatch builder subagent./spec-reviewer-prompt.md - Dispatch spec compliance auditor subagent./code-quality-reviewer-prompt.md - Dispatch code quality auditor subagentYou: I'm using Delegated Execution to implement this plan.
[Read plan file once: docs/plans/feature-plan.md]
[Extract all 5 tasks with full text and context]
[Build task checklist from all tasks]
Task 1: Hook installation script
[Get Task 1 text and context (already extracted)]
[Dispatch builder subagent with full task text + context]
Builder: "Before I start - should the hook install at user level or system level?"
You: "User level (~/.config/godmode/hooks/)"
Builder: "Understood. Implementing now..."
[Later] Builder:
- Implemented install-hook command
- Added tests, 5/5 passing
- Self-review: Noticed I missed --force flag, added it
- Committed
[Dispatch spec compliance auditor]
Spec auditor: PASS - All requirements met, nothing extraneous
[Get git SHAs, dispatch quality auditor]
Quality auditor: Strengths: Good test coverage, clean code. Issues: None. Approved.
[Mark Task 1 complete]
Task 2: Recovery modes
[Get Task 2 text and context (already extracted)]
[Dispatch builder subagent with full task text + context]
Builder: [No questions, proceeds]
Builder:
- Added verify/repair modes
- 8/8 tests passing
- Self-review: All good
- Committed
[Dispatch spec compliance auditor]
Spec auditor: FAIL - Issues:
- Missing: Progress reporting (spec says "report every 100 items")
- Extra: Added --json flag (not requested)
[Builder fixes issues]
Builder: Removed --json flag, added progress reporting
[Spec auditor re-audits]
Spec auditor: PASS - Spec compliant now
[Dispatch quality auditor]
Quality auditor: Strengths: Solid. Issues (Important): Magic number (100)
[Builder fixes]
Builder: Extracted PROGRESS_INTERVAL constant
[Quality auditor re-audits]
Quality auditor: Approved
[Mark Task 2 complete]
...
[After all tasks]
[Dispatch final quality auditor]
Final auditor: All requirements met, ready to merge
Done!
vs. Manual execution:
vs. Task Runner:
Efficiency gains:
Quality gates:
Cost:
Never:
If subagent asks questions:
If auditor finds issues:
If subagent fails the task:
Required workflow skills:
Subagents should use:
Alternative workflow: