what-we-have-to-work

Group unfinished trace.md scenarios into up to three sized work bundles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered, unfinished trace scenarios recorded in docs/*/trace.md into clear, sized work bundles so teams can rapidly choose and start meaningful development tasks without manual triage.

Core Features & Use Cases

  • Survey repository trace files to collect unfinished scenarios, feature context, and size estimates using the provided sizing rubric.
  • Group scenarios into one to three prioritized bundles by feature, dependency chain, or shared code area and provide concise rationale for each option.
  • Use Case: When multiple half-complete features exist, present 1–3 xlarge or large candidate bundles so the team can quickly pick a block of work to execute.

Quick Start

Ask the skill to scan docs/*/trace.md, group unfinished scenarios into up to three work bundles with rationale, and present them for selection.

Frequently Asked Questions about what-we-have-to-work

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

FAQPage Schema
How do I bundle unfinished trace.md scenarios into actionable work chunks?

To bundle unfinished trace.md scenarios, the Skill scans repository docs, collects incomplete items from Implementation Status tables, estimates sizes using a rubric, and groups them into up to three candidate work chunks for selection.

What is the sizing rubric used for task planning in repository trace files?

The task planning sizing rubric scales from tiny to xlarge. The Skill reads Implementation Status tables in trace.md files to estimate task sizes and strictly avoids generating bundles that exceed the xlarge threshold.

How do I group unfinished development tasks by feature and dependency chain?

You can group unfinished development tasks by feature, dependency chain, or shared code areas. The Skill analyzes repository trace files to cluster related scenarios and provides a concise rationale for each grouped work bundle.

Can I use stv:do-work to execute selected work bundles from a backlog scan?

Yes, you can use stv:do-work to execute selected work bundles. After scanning trace.md files and presenting up to three candidates, the Skill invokes stv:do-work or stv:plan-new-task based on your choice and backlog viability.

What is the best way to triage half-complete features recorded in trace files?

The best way to triage half-complete features is scanning docs/*/trace.md files to collect unfinished scenarios, grouping them into one to three prioritized bundles with size estimates, and presenting them for rapid team selection.

Why does my work bundle estimation exceed the xlarge size limit?

Work bundle estimation might exceed the xlarge limit if too many unfinished scenarios are grouped together. The Skill respects the sizing rubric from tiny to xlarge and avoids exceeding xlarge by splitting tasks into smaller candidate chunks.