do-work

Automates unfinished STV trace scenarios from docs/*/trace.md through stv:work and quality gates.

36|3|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/2lab-ai/oh-my-claude --skill do-work-2lab-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-work
Source: https://github.com/2lab-ai/oh-my-claude/tree/main/plugins/stv/skills/do-work
Command: npx skills add https://github.com/2lab-ai/oh-my-claude --skill do-work-2lab-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates implementing unfinished STV trace scenarios by selecting ready items from trace.md, performing the required code changes, enforcing quality gates, and looping until scenarios are complete or human input is required. It removes manual orchestration of multi-file edits, verification, and commit cycles so features are implemented reliably and consistently.

Core Features & Use Cases

  • Task selection & bundling: Scans docs/*/trace.md, extracts and deduplicates File Map entries, prioritizes and bundles scenarios into execution-sized work chunks.
  • Autonomous execution loop: Invokes stv:work to implement scenarios, enforces File Map completion gate, runs gap detection and quality gates, re-runs fixes, and commits when spec requirements are satisfied.
  • Context & decision safety: Manages context budget, applies thresholds for autonomous decisions versus user escalation, and produces structured session reports for handoff.

Quick Start

Run the do-work skill to autonomously implement unfinished scenarios listed in docs/*/trace.md and progress them until the File Map is complete.

Frequently Asked Questions about do-work

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

FAQPage Schema
How do I automate implementation of unfinished trace scenarios in my repository?

Automating trace scenario implementation involves scanning docs/*/trace.md, extracting and deduplicating File Map entries, bundling scenarios into execution-sized chunks, and running an autonomous stv:work loop that enforces quality gates and commits changes.

What is an STV trace scenario and when do I need to run it?

STV trace scenarios are documented in docs/*/trace.md files listing persisted files and side effects. You need this process when unfinished scenarios require iterative code implementation, gap detection, and spec re-verification across a repository.

Do I need a specific file structure to automate code implementation with quality gates?

Yes, your project requires docs/*/trace.md files where scenarios list persisted files and side effects. The automation extracts File Map entries from these docs to bundle work, enforce completion gates, run gap detection, and execute test, build, and lint checks.

What's the best way to handle gap detection and spec re-verification during autonomous coding?

Handling gap detection and spec re-verification requires an autonomous execution loop that invokes stv:work, applies File Map completion gates, runs fixes, and commits changes only when spec requirements are fully satisfied.

When should I expect user intervention during autonomous scenario implementation?

User intervention is required when context thresholds for autonomous decisions are exceeded. The process manages context budget, applies decision safety thresholds, escalates to the user, and produces structured session reports for handoff when scenarios cannot complete automatically.