do-work
Do-Work Skill
A unified entry point for task capture and processing.
Actions:
- do: Capture new tasks/requests → creates UR folder (verbatim input) + REQ files (queue items), always paired, then verifies coverage
- work: Process pending requests → plans (with plan verification), explores, builds, tests
- verify: Evaluate captured REQs against original input → coverage check with auto-fix (also runs automatically after capture)
- cleanup: Consolidate archive → moves loose REQs into UR folders, closes completed URs
Core concept: The do action always produces both a UR folder (preserving the original input) and REQ files (the queue items). Each REQ links back to its UR via
user_requestfrontmatter. This pairing is mandatory for all requests — simple or complex.
Capture ≠ Execute. The do action captures requests. The work action executes them. These are strictly separate operations. After the do action finishes writing files and reporting back, STOP. Do not start processing the queue, do not begin implementation, do not "helpfully" transition into the work action. The user decides when to execute — always. The only exception is if the user explicitly says something like "add this and then run it" or "capture this and start working" in the same invocation.