tracer-dev

Coordinate end-to-end tracer development through a build-validate-review cycle.

24|7|Updated Oct 28, 2014
One-click install
npx skills add https://github.com/ajoslin/dot --skill tracer-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tracer-dev
Source: https://github.com/ajoslin/dot/tree/main/config/opencode/skills/tracer-dev
Command: npx skills add https://github.com/ajoslin/dot --skill tracer-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Tracer Dev Skill coordinates the end-to-end workflow for building tracer bullets, including plan generation, state management, validations, code reviews, demos, and learnings propagation.

Core Features & Use Cases

  • End-to-end workflow: orchestrates plan discovery, state.json updates, PROGRESS.md logging, and learns routing across tracers.
  • Gate-driven execution: enforces the build-validate-review cycle with explicit review steps and outcomes.
  • Documentation and learnings: tracks progress and learnings for future tracers to improve continuity.

Quick Start

Begin by running the tracer workflow to generate a plan and execute the Next-TASK FLOW steps.

Frequently Asked Questions about tracer-dev

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

FAQPage Schema
What is tracer bullet development and when do I need it for my workflow?

Tracer bullet development is an end-to-end workflow that guides feature tracing from plan discovery to code review. You need it to coordinate build-validate-review cycles, enforce state management, and propagate learnings across multiple tracers for consistent delivery.

How do I automate tracer bullet workflows with state management and code review gates?

Automate tracer workflows by running the build-validate-review cycle, which enforces state.json updates, PROGRESS.md logging, and explicit review steps. It coordinates plan generation through code review, ensuring documentation and demos meet delivery requirements.

Can I use this tracer development workflow without external dependencies?

Yes, the tracer development workflow operates with no external dependencies. It internally manages state.json updates, progress logging in PROGRESS.md, and learnings routing across tracers without requiring additional packages or tools.

What's the best way to track progress and propagate learnings across tracer bullets?

Track progress and propagate learnings by enforcing state management through state.json and logging updates in PROGRESS.md. The workflow routes learnings across tracers to improve continuity and ensure consistent delivery on future development cycles.

How does gate-driven execution enforce the build-validate-review cycle?

Gate-driven execution enforces the build-validate-review cycle by requiring explicit review steps and outcomes before progression. It validates state management, demos, and documentation requirements, ensuring each tracer meets consistent delivery standards before moving forward.

Why does my tracer workflow require documentation and demos during development?

Your tracer workflow requires documentation and demos to ensure consistent delivery and track progress for future tracers. PROGRESS.md logging and state management capture learnings that improve continuity across the end-to-end build-validate-review cycle.