do-work

Capture and organize task requests into a structured queue with REQ files.

94|12|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/bladnman/do-work --skill do-work-bladnman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-work
Source: https://github.com/bladnman/do-work/tree/main
Command: npx skills add https://github.com/bladnman/do-work --skill do-work-bladnman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agentic coding tools lose track of ideas, bugs, and feature requests when they arrive faster than they can be acted on. This skill provides a structured task queue that captures requests instantly and processes them thoroughly later, ensuring nothing falls through the cracks.

Core Features & Use Cases

  • Two-phase capture and process workflow: Separate thinking of tasks from executing them, so developers can dump ideas immediately and work through them systematically.
  • Structured request files with full traceability: Every capture creates a User Request folder preserving verbatim input and linked REQ files, maintaining a complete chain from original idea to implementation.
  • Built-in quality gates: Automatic verification of request coverage and plan coverage with auto-fix for gaps, plus complexity-based triage that scales planning depth to the task.
  • Use Case: A developer receives a bug report, a feature idea, and a refactor thought in one conversation. They capture all three instantly with do work, then run do work run later to process each through planning, exploration, implementation, and git commits.

Quick Start

Use the do-work skill to add a request by saying do work add dark mode to the settings page and it will create a structured request file in your project's do-work folder.

Frequently Asked Questions about do-work

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

FAQPage Schema
How do I queue asynchronous feature requests and bug reports for agentic coding tools?

To queue asynchronous feature requests and bug reports for agentic coding tools, you can capture them instantly into a structured task queue and process them later through planning, verification, and git-tracked implementation.

How does a two-phase capture and process workflow handle software development tasks?

A two-phase capture and process workflow separates thinking of software development tasks from executing them, allowing developers to dump ideas immediately and systematically process each through planning, exploration, and git commits later.

What is the best way to maintain traceability from a user request to a git commit?

The best way to maintain traceability from a user request to a git commit is to create structured request files preserving verbatim input and linked REQ documents, ensuring a complete chain from the original idea to implementation.

Does automated task triage scale planning depth for complex coding requests?

Yes, automated task triage scales planning depth for complex coding requests by applying complexity-based triage and built-in quality gates that automatically verify request and plan coverage, applying auto-fix for any gaps.

Do I need file system access to create structured request and UR documents?

Yes, you need file system access to create structured request and UR documents, as the workflow creates a User Request folder and linked REQ files within your project's do-work directory to enforce immutability rules.

Can I spawn subagents for plan and explore phases during task processing?

Yes, you can spawn optional subagents for plan and explore phases during task processing, enabling thorough exploration and structured planning before the agentic coding tool proceeds to implementation and git commits.