doer-implement

To generate a machine-readable patch file and handoff report after implementing code changes, use this Skill to edit code and automatically produce a `patch.diff` and `handoff.json` for downstream evaluation. It also runs targeted smoke tests to verify the updates.

Automating task execution and producing handoff artifacts involves implementing scoped software tasks by editing code and generating standardized files. This Skill executes the task card, runs smoke checks, and outputs `patch.diff` and `handoff.json` to facilitate a clear evaluation process.

Running targeted smoke tests on specific code changes before creating a patch is handled automatically during implementation. The Skill executes checks focused on the touched areas to verify changes and records the outcomes in the final `handoff.json` artifact.

Yes, you can implement a scoped software task and generate a handoff report without manual test configuration. The Skill applies targeted smoke checks automatically based on the touched code areas and outputs the results directly into the `handoff.json` file.

Yes, this implementation Skill supports generating deterministic artifacts for task cards. It satisfies requirements for deterministic artifact generation by consistently producing a standardized `patch.diff` and a `handoff.json` detailing the implementation and smoke check outcomes.

You should not use an automated task implementation tool that generates patch files when a task requires human judgment beyond scoped code edits or lacks clear task card requirements. It is designed for deterministic artifact generation and targeted smoke checks, not open-ended architectural design.