do

Schedule ad-hoc tasks with description-based prompts and every/now/next/stop options.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill do-zillabunny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do
Source: https://github.com/zillabunny/GoblinVolleyball-1.1/tree/main/.claude/skills/do
Command: npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill do-zillabunny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lightweight task management for ad-hoc work, enabling structured research, documentation updates, and content changes without heavy planning.

Core Features & Use Cases

  • Lightweight task dispatcher for ad-hoc work with description-based prompts.
  • Supports scheduling with every/now/next/stop and optional worktrees or pushes.
  • Useful for documentation, small refactors, content updates, or newsletter entries.

Quick Start

Ask Claude to create a simple ad-hoc task with a description and optional scheduling.

Frequently Asked Questions about do

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

FAQPage Schema
How do I schedule ad-hoc tasks for Claude workflows without heavy planning?

Scheduling ad-hoc tasks for Claude workflows is handled through a lightweight dispatcher using description-based prompts with every, now, next, and stop commands. This enables structured documentation and refactoring updates without requiring heavy upfront project planning.

Can I use git worktree isolation for automated content updates?

Git worktree isolation is supported as an optional feature when dispatching automated content updates. This allows each task to run in an isolated worktree, preventing conflicts during concurrent documentation changes or small refactors.

What is the best way to automate recurring newsletter entries with Claude?

Automating recurring newsletter entries is best achieved by combining description-based prompts with the recurring scheduling option. This dispatches content generation tasks at set intervals, applying structured prompts to produce consistent newsletter updates.

Does this task dispatcher support pushing changes directly after a refactor?

Direct push options are supported after completing tasks like small refactors or content updates. The dispatcher integrates push functionality alongside optional worktree isolation, allowing automated changes to be committed and pushed without manual intervention.

What are the limitations of using lightweight task dispatch for complex refactoring?

Lightweight task dispatch is designed for ad-hoc work like documentation and small refactors, not complex refactoring. It lacks heavy planning features, so large-scale architectural changes may exceed its structured prompt and recurring scheduling capabilities.