do-work

Execute development tasks from a scratchpad with atomic commits.

1|Updated Dec 28, 2025

Search Tags:#automation #scratchpad #TodoWrite #branch-management #atomic-commits #execute #issue-workflow

Ready to run

npx skills add https://github.com/fusupo/escapement --skill do-work

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: do-work
Source: https://github.com/fusupo/escapement/tree/main/skills/do-work
Command: npx skills add https://github.com/fusupo/escapement --skill do-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the execution of development work from a scratchpad, providing structured progress tracking and atomic commits.

Core Features & Use Cases

Load and execute tasks from the scratchpad, updating a TodoWrite-style progress tracker.
Coordinate atomic commits after each completed task and integrate with setup-work and PR workflows.
Resume sessions across restarts and handle blockers via guided prompts.

Quick Start

Start work on issue #42 to begin a structured execution session. The skill will load the scratchpad, create TodoWrite items, guide task execution, and commit changes after each task.

Frequently Asked Questions about do-work

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

FAQPage Schema

How do I automate development work execution from a scratchpad with atomic commits?▼

Automating scratchpad work execution with atomic commits involves loading tasks into a progress tracker and committing changes after each item completes. This approach structures issue-based workflows by coordinating iterative task loops and guided session resumption.

What is the best way to manage an iterative work loop for issue-based software workflows?▼

Managing an iterative work loop for issue workflows requires initializing a TodoWrite-style tracker to monitor progress. The process loads scratchpad tasks, executes them sequentially, and orchestrates commits upon completion of each individual task.

Can I resume a development work session across restarts using a scratchpad?▼

Resuming a development work session across restarts is supported by loading the existing scratchpad state. The workflow handles blockers via guided prompts, allowing you to continue task execution and coordinate remaining atomic commits without losing progress.

Does this scratchpad execution workflow support complex tasks requiring plan mode?▼

Complex tasks within scratchpad execution are handled using EnterPlanMode to break down intricate requirements. Exploration can be delegated via Task tools, ensuring comprehensive task analysis before integrating the results into the main iterative work loop.

How do I integrate commit-changes and create-pr workflows into task execution?▼

Integrating commit-changes and create-pr workflows happens automatically after each scratchpad task completes. The execution process orchestrates these actions to ensure atomic commits are traceable and pull request creation is coordinated with the issue workflow.

When do I need atomic commits for issue-based software workflows?▼

Atomic commits for issue-based workflows are needed when you require traceable progress for individual development tasks. This method ensures each completed item from the scratchpad is committed separately, providing clear history and structured session management.