DB

do-work (Capture + Build)

A two-skill Claude Code system that separates idea capture from execution — one Claude captures ideas into a queue in real time, another works through that queue autonomously.

Developer Tools / Workflowdeveloper-toolsworkflow
Or just install the prompt above — no subscription needed

About this skill


name: do-work description: Use when A two-skill Claude Code system that separates idea capture from execution — one Claude captures ideas into a queue in real time, another works through that queue autonomously.

do-work (Capture + Build)

do-work is a two-terminal workflow built entirely through conversation with Claude Code, no hand-written code. One skill (capture) takes ideas the moment you have them and drops them into a shared folder-based queue. The other skill (build) runs continuously, pulling from that queue, planning when needed, spinning up sub-agents to build and test, and committing automatically — looping until the queue is empty.

What you get

  • Two markdown skill files (capture + build) plus the folder-based queue pattern connecting them, from the open-source repo.

Customize your output

  • What counts as a task in the queue
  • when the build agent should plan vs. just execute
  • commit/test conventions.

Example output

A live two-terminal setup where ideas typed in one window are automatically built, tested, and committed by the other.

Best for

Developers and engineers using Claude Code, Cursor, or similar AI coding assistants who want an autonomous build loop.


Source: Matt Maher (bladnman) · https://www.youtube.com/watch?v=I9-tdhxiH7w Category: Developer Tools / Workflow · Priority: Standard

SKILL.md preview

---
name: do-work
description: Use when A two-skill Claude Code system that separates idea capture from execution — one Claude captures ideas into a queue in real time, another works through that queue autonomously.
---

# do-work (Capture + Build)

do-work is a two-terminal workflow built entirely through conversation with Claude Code, no hand-written code. One skill (capture) takes ideas the moment you have them and drops them into a shared folder-based queue. The other skill (build) runs continuously, pulling from that queue, planning when needed, spinning up sub-agents to build and test, and committing automatically — looping until the queue is empty.

## What you get

- Two markdown skill files (capture + build) plus the folder-based queue pattern connecting them,...