Agent skill
implement
Use when executing an implementation plan — dispatches subagent per task with self-review, verification along the way, and commits
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/implement-dodi-hq-dodi-skills
SKILL.md
Implement
Execute a plan by dispatching a fresh subagent per task. Each subagent implements, tests, self-reviews, and commits. No heavy review gates per task — the full review happens after all tasks complete (see dodi-dev:review).
Process
- Read the plan, extract all tasks with full text
- For each task sequentially: a. Dispatch implementer subagent with full task text + context (see implementer-prompt.md) b. Handle subagent status (see below) c. Mark task complete
- After all tasks: invoke
dodi-dev:review
Never dispatch multiple implementers in parallel — they'll conflict.
Model Selection
- Mechanical tasks (1-2 files, clear spec): use a fast model
- Integration tasks (multi-file, pattern matching): use standard model
- Architecture/judgment tasks: use most capable model
Handling Implementer Status
| Status | Action |
|---|---|
| DONE | Mark complete, next task |
| DONE_WITH_CONCERNS | Read concerns. If correctness issue, address first. If observation, note and proceed |
| NEEDS_CONTEXT | Provide missing context, re-dispatch |
| BLOCKED | Assess: provide more context, use more capable model, break task smaller, or escalate to human |
Never ignore an escalation or retry without changes.
Verification Along the Way
After each subagent completes, verify its claims before moving on:
- Check
git difforgit logto confirm changes were actually made - If the task included tests, confirm they actually ran and passed
- Don't trust "tests pass" without evidence
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?