implement

Claim highest-priority Drover tickets, create worktrees, and run quality checks.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/cosmicdreams/claude-plugins --skill implement-cosmicdreams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/drover/skills/implement
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill implement-cosmicdreams

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It accelerates fixing newly identified issues by autonomously selecting a highest-priority ready ticket, preparing an isolated worktree, attempting code changes, and moving the ticket into a human review lane with structured results.

Core Features & Use Cases

  • Claims and processes one lane-ready ticket per run: Automatically picks the top unassigned ticket by severity and age to keep execution focused and predictable.
  • Creates an isolated worktree and executes a fix workflow: Validates project root state, spawns a dedicated implementer-agent, and runs quality checks before advancing the ticket.
  • Writes structured projected solution metadata and notifies for review: Appends the Projected Solution block (for later recall/verification) and moves the ticket to lane-awaiting-review, optionally sending a Slack DM to a configured reviewer.

Quick Start

Grant the required Drover permissions and run the skill when you receive a drover READY notification, or simply invoke it directly to attempt a fix for the next highest-priority lane-ready ticket.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate fix attempts for Drupal tickets using an isolated worktree?

To automate fix attempts for Drupal tickets, this Skill claims the highest-priority unassigned ticket, creates an isolated worktree, attempts code changes, and runs quality checks before handing off to review.

What are the requirements for running an automated ticket triage workflow in DDEV?

Automated ticket triage in DDEV requires valid Drover configuration, Beads board initialization, a non-dirty project root git state, and granted permissions for worktree creation, source editing, and DDEV execution.

How does AI-assisted ticket triage select which issue to fix next?

AI-assisted ticket triage selects the next issue to fix by strictly filtering lane-ready tickets by severity and age, claiming only the single highest-priority unassigned ticket per run to keep execution focused.

Can I use automated code fixes for Drupal repositories without manual review?

Automated code fixes for Drupal repositories always require manual review, as the workflow moves completed attempts to a lane-awaiting-review state and optionally sends a Slack DM with structured Projected Solution notes to a reviewer.

What happens if my project root git state is dirty when starting an automated fix workflow?

An automated fix workflow cannot start if the project root git state is dirty, as the Skill requires a clean repository to safely create a guarded worktree and attempt source edits without conflicting with existing changes.

Does automated ticket triage work with non-Drupal repositories?

Automated ticket triage applies specifically to Drupal and DDEV-based repositories where teams have granted source editing and DDEV-exec permissions, making it unsuitable for non-Drupal environments.