skills.rest
2lab-ai
2lab-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

work

Implement code scenarios from trace.md until contract tests pass.

36|3|Updated Jan 6, 2026
Search Tags:#implementation#code-quality#backtracking#contract-tests#stv#trace-driven#trace-verify
One-click install
npx skills add https://github.com/2lab-ai/oh-my-claude --skill work-2lab-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work
Source: https://github.com/2lab-ai/oh-my-claude/tree/main/plugins/stv/skills/work
Command: npx skills add https://github.com/2lab-ai/oh-my-claude --skill work-2lab-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates trace-driven implementation by guiding developers to implement features scenario-by-scenario so that contract tests turn GREEN and the code matches the trace document, preventing undetected drift between design artifacts and implementation.

Core Features & Use Cases

  • Scenario-by-scenario implementation: Re-reads each scenario's trace and implements only the specified behavior until contract tests pass.
  • Trace conformance verification: Runs a seven-section verification (API, Input, Layer Flow, Side Effects, Error Paths, Output, Observability) to detect mismatches and enforce synchronization between trace and code.
  • Artifact backtrack & gap detection: Detects spec/trace gaps, records deviations, and applies a defined backtrack protocol to update upstream artifacts before fixing code.

Quick Start

Run the work skill to implement the first scenario in trace.md and iterate until the contract tests for that scenario are GREEN.

Frequently Asked Questions about work

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

FAQPage Schema
How do I ensure my code matches trace-driven development specifications?▼

Trace-driven development ensures code matches specifications by executing features scenario-by-scenario using a trace document to drive implementation order and verify conformance through contract tests.

What is trace conformance verification in software engineering?▼

Trace conformance verification is a seven-section audit checking API, Input, Layer Flow, Side Effects, Error Paths, Output, and Observability to detect mismatches and enforce synchronization between trace documents and code.

How do I implement features scenario-by-scenario until contract tests pass?▼

You implement features scenario-by-scenario by reading trace.md and spec.md, implementing only the specified behavior for each scenario, and iteratively running contract tests until they turn GREEN before moving forward.

What should I do when I detect gaps between spec and trace documents?▼

When detecting spec/trace gaps, you apply a defined backtrack protocol to record deviations and update upstream artifacts before fixing code, preventing undetected drift between design artifacts and implementation.

Do I need spec.md and trace.md files to run trace-driven implementation?▼

Yes, trace-driven implementation requires reading spec.md for feature specifications and trace.md for execution scenarios, using both to drive implementation order, enforce mandated signatures, and perform conformance verification with file map coverage.

Why does my implementation drift from the design artifacts during development?▼

Implementation drifts from design artifacts when features are not executed scenario-by-scenario against a trace document, which is prevented by running iterative contract tests and applying a backtrack protocol to update upstream artifacts before fixing code.

Related Skills

Explore More Software Engineering Skills→
2lab-ai2lab-ai
36

trace

Generate vertical traces and RED contract tests from feature specs.

Official
Advanced
2lab-ai2lab-ai
36

do-work

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

Official
Advanced
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced
jayhjenkinsjayhjenkins

test-driven-development

Enforce red-green-refactor cycles with tests guiding code implementation.

Community
Basic