drone

Claim unblocked epic subtasks and implement them within the declared file scope.

Updated Mar 26, 2026

Search Tags:#task-management #epic #drone #code-implementation #subtask #local-verification

Ready to run

npx skills add https://github.com/benediktms/overmind --skill drone

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: drone
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/drone
Command: npx skills add https://github.com/benediktms/overmind --skill drone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Activates the drone persona to automatically claim unblocked subtasks from the shared epic task list, implement them within the declared file scope, verify locally, and hand them back as done, reducing manual task-switching and coordination overhead.

Core Features & Use Cases

Automated task claiming: identify the next ready subtask with no owner and no blockers, then claim it for implementation.
Scoped execution: edits are confined to the declared file scope to minimize risk and avoid cross-file changes.
Local verification & handoff: verify changes locally and hand off completion to the lead, enabling smooth task progression.

Quick Start

Ask the drone to claim the next ready subtask from the epic list and implement it within the declared file scope, then verify locally.

Frequently Asked Questions about drone

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

FAQPage Schema

How do I automate claiming and implementing unblocked subtasks from an epic task list?▼

To automate claiming and implementing unblocked subtasks, this workflow identifies the next ready subtask with no owner or blockers, claims it, and implements the code within the declared file scope. It then performs local verification and hands the completed task back to the lead.

How does scoped execution work for automated subtask implementation?▼

Scoped execution for subtask implementation confines all code edits to the declared file scope. This mechanism minimizes risk and prevents cross-file changes, ensuring the automated task workflow strictly adheres to the predefined boundaries of the specific subtask.

What is the best way to handle local verification and task handoff in a sprint workflow?▼

The best way to handle local verification and task handoff is to verify changes locally after implementation and then mark the subtask as done. This ensures orderly handoff to the lead, enabling smooth and continuous task progression within the sprint.

Do I need clearly defined and unblocked tasks to use automated subtask claiming?▼

Yes, you need clearly defined and unblocked tasks to use automated subtask claiming. This workflow is applicable to sprint task workflows where subtasks are explicitly marked as ready, have no blockers, and require implementation within a shared epic.

Can I use this automated task workflow for cross-file changes outside the declared scope?▼

No, you cannot use this workflow for cross-file changes outside the declared scope. It enforces strict file-scope adherence to minimize risk, meaning all automated edits are confined exclusively to the files declared for the specific subtask.