implementing

Implement scoped issues by making code changes, verifying, and opening a draft pull request.

Updated Apr 14, 2026

Search Tags:#testing #pull request #implementation #verification #handoff

Ready to run

npx skills add https://github.com/arthur-debert/dodot --skill implementing-arthur-debert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementing
Source: https://github.com/arthur-debert/dodot/tree/main/.agents/skills/implementing
Command: npx skills add https://github.com/arthur-debert/dodot --skill implementing-arthur-debert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps an implementer turn a scoped issue or workstream into a tested code change, a draft pull request, and a clean handoff without drifting into coordination or review management.

Core Features & Use Cases

Scoped implementation: Make the requested change inside the assigned tree and branch while staying within the brief’s decision boundaries.
Verification discipline: Run the exact verification commands required by the brief and validate the change before opening the PR.
Draft PR handoff: Open one draft PR with context, note what is out of scope, and run the PR engine once so initial routing can begin.
Use case: An agent is assigned a bug fix or feature slice, updates the code and tests, verifies the result, and leaves a complete draft PR for the next stage.

Quick Start

Implement the assigned issue, verify it with the provided commands, open a draft PR with context, run the PR engine once, and then stop.

Frequently Asked Questions about implementing

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

FAQPage Schema

How do I implement a scoped issue and open a draft pull request?▼

To implement a scoped issue, make the code change within the assigned tree and branch, verify it using brief-provided commands, and open a draft pull request with handoff context. This keeps implementation focused on the assigned workstream without drifting into review coordination.

What is the best way to hand off a verified code change to a draft PR?▼

The best way to hand off a verified code change is to run the exact verification commands required by the brief, validate the scoped diff, and open one draft pull request with context. Note what is out of scope and run the PR engine once for initial routing.

Does this implementation workflow handle pull request review coordination or merge duties?▼

No, this implementation workflow does not handle review coordination or merge duties. It applies to role-scoped implementation tasks that require staying inside an assigned tree and branch, focusing solely on making the code change, verifying it, and opening a draft pull request for handoff.

Why do I need to run verification commands before opening a draft PR for my implementation?▼

You need to run verification commands before opening a draft PR because verification discipline ensures the scoped implementation is validated against the brief's requirements. This prevents unverified changes from being routed for review, maintaining a clean handoff for the next stage.

Can I use this approach for a bug fix or feature slice that needs testing and handoff?▼

Yes, you can use this approach for a bug fix or feature slice. An agent updates the code and tests, verifies the result with the provided commands, and leaves a complete draft pull request with handoff context for the next stage, ensuring disciplined implementation.

When should I avoid using a scoped draft PR workflow for implementation?▼

You should avoid using a scoped draft PR workflow when a task requires review coordination, merge duties, or decisions outside the brief's assigned tree and branch. This workflow is strictly for making scoped code changes, verifying them, and handing off via a draft pull request.