implementer

Executes one dependency-ready micro-task and records implementation results with evidence.

2|1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/AutoByteus/autobyteus-agents --skill implementer-autobyteus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementer
Source: https://github.com/AutoByteus/autobyteus-agents/tree/main/agent-teams/evidence-driven-delivery-team/agents/implementer/skills/implementer
Command: npx skills add https://github.com/AutoByteus/autobyteus-agents --skill implementer-autobyteus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In multi-agent delivery workflows, implementation work often drifts beyond its assigned scope, loses traceability, or proceeds without verifying task readiness. This Skill enforces disciplined execution of a single planned micro-task while producing a structured, evidence-backed result for downstream validation. ## Core Features & Use Cases - Scoped Task Execution: Implements only the assigned micro-task from the approved plan, without redefining scope, inventing behavior, or taking over planning and validation ownership. - Experiment Guardrails: Confirms budgets, checkpoints, stop conditions, and success thresholds before running hypothesis-driven or costly tasks, and stops cleanly when limits are hit. - Structured Result Reporting: Produces an implementation-result.md from a template capturing changed paths, checks run, deviations, gate results, and remaining risks. - Use Case: In an evidence-driven delivery team, the implementer agent picks up a ready task from the planner, makes the code changes, runs implementation-scoped checks, and hands a complete result record to the validator. ## Quick Start Implement the assigned micro-task from the current plan and produce an implementation-result.md documenting changed paths, checks, and deviations.

Frequently Asked Questions about implementer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a planned micro-task without scope creep?▼

Read the current plan revision, task dependencies, and expectation first, then implement only the assigned scope. Record changed paths and check results in the implementation-result template so deviations are explicit rather than silent.

What should an implementation result report include?▼

Include the plan ID, task ID, task expectation, changed paths, actual result, implementation-scoped checks and commands, deviations, remaining risks, and whether the output is ready for validation. The provided template standardizes these fields.

When should implementation stop and return to the planner?▼

Stop when a stop condition triggers, the budget or checkpoint is exhausted, a prerequisite gate fails, or the task proves too expensive or low-value for its micro-task boundary. Return a planning result instead of forcing an implementation workaround.

Does this skill handle validation of its own output?▼

No. The implementer runs only implementation-scoped checks and records their results. Broad validation and acceptance of the result are owned by the Validator role, keeping responsibilities separated.

When do experiment guardrails like budgets and checkpoints apply?▼

They apply when a task is hypothesis-driven, costly, irreversible, or explicitly benchmarked. For ordinary non-experiment tasks, do not invent an experiment ladder; just implement the scoped work and record results.