Execute an approved implementation plan at the context boundary that preserves required independence and review. Use when implementing plans, executing multi-task PRs, choosing between main-loop and dispatched execution, or transitioning from planning to implementation.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Execute a multi-task plan with one implementation owner per slice, independent review after each task, and whole-branch review before completion.
Choose placement before any edit. Delegate only for a named benefit: independent parallel work over disjoint owned paths verifiable alone; measured context pressure; a required independent verification gate owned by someone other than the implementer; or host-enforced permission isolation, because prompt text is not enforcement. A specialist label, workflow stage, file count, plan length, or "more thorough" fan-out is not a named benefit. Precedence, first match wins: controlling host authority, then required independence or isolation, then coupling and verifiability, then economical eligible capability (common-task-complexity-routing).
| Condition | Placement |
|---|---|
| Coupled sequential reasoning; host permits main-loop implementation | One implementation context, skills loaded progressively |
| Independent, bounded, verifiable slices with disjoint ownership | Concurrent bounded workers, one owner per component |
| Host requires worker execution | That boundary; keep coupled steps in one bounded worker, not a planner/fixer chain |
| Isolation or permission needed but unavailable | Report unsupported or blocked; never infer permission |
Under an active host or orchestration policy requiring an execution confirmation gate before multi-task implementation:
One implementation context is not one actor for the lifecycle: main-loop implementation still requires a separate reviewer, so implementer self-review never closes a review gate. Missing approval, packet, standards, or isolation blocks only the affected operation: report the exact missing item, never infer permission or silently change the path. Plan approval authorizes neither merge, deployment, premium spend, nor a different execution mode. Detail: methodology.md.
Report current state read-only with status --state <PATH> --revision <REV> --dirty-identity <ID> --format json|markdown; it rechecks plan and evidence bytes and never mutates state. Checkpoint completion is neither verification, acceptance, nor release.
BASE=$(git rev-parse HEAD). Generate the brief from the repository root: python3 skills/common/common-subagent-driven-development/scripts/task_brief.py <PLAN_FILE> <TASK_NUMBER> --assignment <ASSIGNMENT_JSON> [--out <BRIEF_FILE>]. --assignment is required; task_brief.py validates the manifest and the selected task section's contract fields (scope/owned write set, inputs, outputs, real ingress, positive/negative invariants, verification owner, explicit handoff/freeze, correction route) before publishing, and rejects missing fields or fields that appear only inside code fences (exit 2).wait() and yield control; never poll status or activity in a loop.$BASE over the owned paths: python3 skills/common/common-subagent-driven-development/scripts/review_package.py <PLAN_FILE> $BASE WORKSPACE --paths <OWNED_PATHS...>. Pass literal file paths or bounded owned directories (no pathspec magic, globs, ., or overlapping scopes); same-base/scope packages are cumulative, not fix-only. Dispatch an independent reviewer with [BRIEF_FILE], [REPORT_FILE], [DIFF_FILE].$BASE with identical owned paths, and re-review the latest cumulative state.| Observed failure | Route |
|---|---|
| Missing prerequisite or context | needs_context or blocked naming the exact missing item; no provider fallback |
| Defective output | One corrective assignment naming the failed AC and expected observable result |
| Observed provider exhaustion | Only an eligible, authorized fallback; the receipt records the exhaustion evidence and selected route |
| Consequential safety or design issue | Human decision |
Retry count alone never authorizes premium, timeout and cancellation are not completion, and required human approvals stay external to agent verdicts. Rules and examples: methodology.md.
Run whole-branch review from the repository root with python3 skills/common/common-subagent-driven-development/scripts/review_package.py <PLAN_FILE> $MERGE_BASE HEAD, dispatch an independent senior reviewer, then complete the branch.
Cleanup needs a verified durable archive and ownership authority: before deleting <workspace>, verify every report, diff, receipt, and evidence copy is archived outside the scratch directory. Never erase the only evidence copy; if archive verification fails or authority is missing, retain <workspace> and report the unarchived evidence. Once verified and authorized, delete <workspace>.
<workspace> without verified durable archival and ownership authority.Methodology & Gates · Prompt Templates · Progress Receipts · Capability & Effort Resolution
HoangNguyen0403/agent-skills-standard
cd1e988
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.