Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Execute implementation plans by dispatching a fresh subagent per task with two-stage review (spec compliance then code quality). Use when you have an implementation plan with mostly independent tasks and want high-quality, fast iteration within a single session.
Execute implementation plans by dispatching a fresh subagent per task with two-stage review (spec compliance then code quality). Use when you have an implementation plan with mostly independent tasks and want high-quality, fast iteration within a single session.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Execute a plan by dispatching a fresh subagent per task, with two-stage review after each β spec compliance first, then code quality. Core principle: Fresh subagent per task + two-stage review = no context pollution, high quality, fast iteration.
npx clawhub@latest install subagent-driven-development
You have an implementation plan with discrete, mostly independent tasks You want to execute the plan within a single session (no human-in-the-loop between tasks) Tasks can be implemented and reviewed sequentially without tight coupling ConditionThis SkillAlternativeHave a plan, same sessionYesβHave a plan, parallel sessionNoexecuting-plansNo plan yetNoWrite a plan firstTasks tightly coupledNoManual execution or decompose more
βββββββββββββββββββββββββββββββββββββββββββββββββββββββ β 1. Read plan, extract ALL tasks with full text β β 2. Note shared context (arch, deps, conventions) β β 3. Create TodoWrite with all tasks β ββββββββββββββββββββββββ¬βββββββββββββββββββββββββββββββ βΌ βββββββ Per Task βββββββ β β β Dispatch Implementer (references/implementer-prompt.md) β β β β βΌ β β Questions?ββyesβββΊ Answer, re-dispatchβ β βno β β βΌ β β Implement + test + commit + self-reviewβ β β β β βΌ β β Dispatch Spec Reviewer (references/spec-reviewer-prompt.md) β β β β βΌ β β Compliant?ββnoβββΊ Implementer fixesβββ β βyes then re-review β βΌ β Dispatch Code Reviewer (references/code-quality-reviewer-prompt.md) β β β βΌ β Approved?ββnoβββΊ Implementer fixes, re-review β βyes β βΌ β Mark task complete βββββββββ¬βββββββββββββββ βΌ More tasks? ββyesβββΊ next task βno βΌ Final cross-task code review βΌ Finish development branch
Three reference prompts are provided for the subagent roles: RoleFilePurposeImplementerreferences/implementer-prompt.mdImplement, test, commit, self-reviewSpec reviewerreferences/spec-reviewer-prompt.mdVerify code matches spec exactlyCode reviewerreferences/code-quality-reviewer-prompt.mdVerify code is clean and maintainable
Controller: Reading plan β 5 tasks extracted, TodoWrite created. βββ Task 1: Hook installation script βββ [Dispatch implementer with full task text + context] Implementer: "Should the hook be installed at user or system level?" Controller: "User level (~/.config/hooks/)" Implementer: β Implemented install-hook command - Added tests (5/5 passing) - Self-review: missed --force flag, added it - Committed [Dispatch spec reviewer] Spec reviewer: β Spec compliant β all requirements met [Dispatch code reviewer with git SHAs] Code reviewer: β Approved β clean, good coverage [Mark Task 1 complete] βββ Task 2: Recovery modes βββ [Dispatch implementer] Implementer: β Added verify/repair modes (8/8 tests passing) [Dispatch spec reviewer] Spec reviewer: β Issues: - Missing: progress reporting ("report every 100 items") - Extra: added --json flag (not in spec) [Implementer fixes: remove --json, add progress reporting] Spec reviewer: β Spec compliant [Dispatch code reviewer] Code reviewer: Important β magic number 100, extract constant [Implementer fixes: extract PROGRESS_INTERVAL] Code reviewer: β Approved [Mark Task 2 complete] ... (tasks 3-5) ... [Final cross-task code review] Final reviewer: β All requirements met, ready to merge
The controller (you) orchestrates the flow. Key duties: ResponsibilityDetailExtract tasks upfrontRead plan once, extract all task text β subagents never read the plan fileProvide full contextGive each subagent the complete task text + architectural contextAnswer questionsRespond clearly and completely before letting subagent proceedEnforce review orderSpec compliance first, code quality second β never reversedTrack progressUpdate TodoWrite after each task completesDispatch sequentiallyOne implementation subagent at a time to avoid conflicts
Each task passes through three quality checks: GateWhoWhatSelf-reviewImplementerCompleteness, naming, YAGNI, test qualitySpec reviewSpec reviewerMatches requirements exactly β nothing more, lessCode reviewCode reviewerClean code, maintainability, test coverage
vs. manual execution: Fresh context per task (no confusion from accumulated state) Subagents follow TDD naturally Questions surfaced before work begins, not after vs. parallel-session plans: No handoff overhead Continuous progress Review checkpoints are automatic Cost trade-off: More subagent invocations (implementer + 2 reviewers per task), but catches issues early β cheaper than debugging later.
Skip either review β both spec compliance and code quality are mandatory Start code review before spec review passes β wrong order wastes effort on code that doesn't meet spec Dispatch multiple implementers in parallel β causes merge conflicts and context corruption Make subagents read the plan file β provide full task text directly Skip scene-setting context β subagent needs to understand where the task fits architecturally Ignore subagent questions β answer fully before they proceed Accept "close enough" on spec compliance β if the reviewer found issues, it's not done Skip re-review after fixes β reviewer found issues β implementer fixes β reviewer reviews again Let self-review replace actual review β self-review is a first pass, not a substitute Move to next task with open review issues β current task must be fully approved first Fix issues manually instead of through a subagent β manual fixes pollute controller context
SituationResponseSubagent asks questionsAnswer clearly, provide additional context if neededReviewer finds issuesSame implementer subagent fixes, reviewer re-reviewsSubagent fails task entirelyDispatch a new fix subagent with specific instructionsTask blocked by dependencyReorder remaining tasks or resolve dependency first
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.