tracebound

Use this skill whenever the user wants to implement an approved fix spec for a failure mode and verify that it works. Trigger on phrases like "implement fm_…", "start the implementation for fm_…", "the spec is approved, proceed", "implement and verify fm_…", or any request to move a failure mode from spec_approved into implemented and verified state. Requires a SPEC.md that has been approved (status fix_approved). Use research-failure-mode first if no spec exists yet.

Use this skill whenever the user wants to investigate a failure mode, understand its root cause, gather evidence from traces, identify what SME input is needed, and draft a fix spec for human review. Trigger on phrases like "research fm_…", "investigate this failure mode", "draft a spec for fm_…", "understand why fm_… is happening", "what's causing fm_…", or any request to move a failure mode from discovered/triaged into a specced, reviewable state. This skill is read-only with respect to agent code — it only reads traces, source, and config, then writes a SPEC.md and updates failure_modes.json status. Use implement-failure-mode after the spec is approved.

Use this skill whenever the user asks to analyze, classify, cluster, or harvest failure modes from a Tracebound trace file (JSONL under `tracebound/<agent>/traces/`). Trigger on phrases like "run analyze-traces", "process this langfuse dump", "cluster the failures in traces/foo.jsonl", "update failure_modes.json from these traces", or any request to batch-process production agent traces into a failure-mode catalogue. The skill takes ONE agent and ONE trace file per invocation, filters traces with negative feedback signals, classifies each into existing or newly-created failure modes (biased toward reuse), and writes back enriched traces + an updated `failure_modes.json` — running `tracebound validate --agent <agent>` after every batch and self-correcting until it passes.

Use this skill whenever the user wants to create a Tracebound adapter — a CLI script that reads a raw traces file (JSON or JSONL) from a third-party system and converts it into the Tracebound on-disk format (one JSONL index file under `tracebound/<agent>/traces/` + one raw file per trace under `tracebound/<agent>/traces/original/`). Trigger on phrases like "create an adapter for…", "write a converter for my traces", "I have traces from X, help me import them", "build an adapter script", or "convert this JSON dump to Tracebound format". The skill inspects a concrete example of the source data, designs the field mapping, and generates a ready-to-run CLI script scoped to one agent.

Write and run Node.js CLI scripts using modern built-in APIs. Use when the user asks to build or run a CLI tool, one-off script, or automation task in Node.js. Enforces zero-dependency best practices: built-in argument parsing (parseArgs), util.styleText for terminal colors, and native Node.js APIs instead of third-party packages.