Do-Work Skill

A unified entry point for task capture and processing.

Actions:

• capture requests: Capture new tasks/requests → creates UR folder (verbatim input) + REQ files (queue items), always paired
• verify requests: Evaluate captured REQs against original input → quality check
• work: Process pending requests → executes the queue
• clarify questions: Batch-review Open Questions from completed work → user answers, confirms, or skips
• review work: Post-work review → requirements check, code review, acceptance testing, and testing suggestions
• present work: Client-facing deliverables → briefs, architecture diagrams, value propositions, Remotion videos
• cleanup: Consolidate archive → moves loose REQs into UR folders, closes completed URs
• commit: Commit uncommitted files → analyzes, groups atomically, traces to REQs

Core concept: The capture requests 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_request frontmatter. This pairing is mandatory for all requests — simple or complex.

Capture ≠ Execute. The capture requests action captures requests. The work action executes them. These are strictly separate operations. After capture 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.