Generate vertical traces and RED contract tests from feature specs.
npx skills add https://github.com/2lab-ai/oh-my-claude --skill trace-2lab-ai
Please help me install this Agent Skill. Skill: trace Source: https://github.com/2lab-ai/oh-my-claude/tree/main/plugins/stv/skills/trace Command: npx skills add https://github.com/2lab-ai/oh-my-claude --skill trace-2lab-ai
This Skill automates the creation of comprehensive vertical traces and RED contract tests from feature specs, eliminating manual, error-prone mapping between API requests and persisted state so teams can detect transformation bugs early.
Use the trace skill to read docs/my-feature/spec.md, generate docs/my-feature/trace.md, and scaffold RED contract tests for each scenario.
High-intent search queries and answers about installing and using this skill.
To generate failing contract tests from API specs, apply a spec-driven trace skill to your spec.md file. It extracts endpoint scenarios and outputs RED contract tests that purposely fail until your implementation matches the documented request-to-database parameter transformations.
Vertical tracing for API scenarios is documenting the end-to-end parameter transformation chain from API request fields to database columns. It maps input validation, per-layer transformations, side effects, error paths, and observability across handlers, services, and repositories into a structured trace.md file.
Map request parameters to database columns by analyzing your feature spec and codebase to locate relevant handlers and repositories. This produces a vertical trace documenting transformation arrows across each layer, ensuring end-to-end parameter mapping from Request fields to persisted DB columns.
Track changes to API parameter transformations using a Delta Protocol changelog. When your feature spec evolves, the vertical trace and corresponding contract tests are updated while maintaining a Delta Protocol changelog to support continuous trace evolution and change tracking.
Yes, you need a spec.md file listing endpoints and user stories to generate API contract tests. The skill reads this feature spec to derive scenario lists, parameter transformation arrows, side effects, and error paths required to scaffold the RED tests and vertical trace documentation.
The contract tests generated for API scenarios include happy, sad, side-effect, and contract test types. These failing tests verify end-to-end parameter transformation chains, validating input validation, side effects, and error paths until your implementation matches the derived vertical trace.
danielcastro-devDraft collaborative feature plans with clarifying questions to .speclet/draft.md.
JoeGaebelOrchestrate Outside-In TDD workflows from end-to-end tests to unit tests.
jhlee0409Analyze FSD layer structure and enumerate slices, segments, and public APIs.
shafibabarValidate FastAPI implementations against hand-authored OpenAPI contracts.
