tracer-bullets

Build a thin end-to-end slice across DB, API, WebSocket, and Client layers.

2|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/eins78/agent-skills --skill tracer-bullets-eins78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tracer-bullets
Source: https://github.com/eins78/agent-skills/tree/main/skills/tracer-bullets
Command: npx skills add https://github.com/eins78/agent-skills --skill tracer-bullets-eins78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tracer Bullets solve architectural uncertainty by forcing a single, end-to-end implementation that validates integration across all system layers before widening.

Core Features & Use Cases

  • Build one thin vertical slice that traverses DB → API → WebSocket → Client.
  • Validate architecture through real integration, not proofs or mocks.
  • Use as a planning tool to narrow scope and then widen.

Quick Start

On a feature branch, run the tracer bullets workflow to produce a validated end-to-end slice.

Frequently Asked Questions about tracer-bullets

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

FAQPage Schema
How do I validate architecture across multiple system layers before building out a full feature?

Building a tracer bullet means implementing a single end-to-end vertical slice across all layers, such as DB to API to Client. You write production-ready code with minimal error handling to validate the full architecture path before widening the feature.

What is a tracer bullet in software engineering and when should I use it?

A tracer bullet is a single, end-to-end implementation that validates integration across all system layers. Use it for large multi-layer features where the path is not well established across DB, API, WebSocket, and Client to solve architectural uncertainty.

Can I use mocks when building a tracer bullet to test system integration?

No, tracer bullets validate architecture through real integration, not proofs or mocks. You must build production-ready tracer code that touches every layer to ensure the end-to-end path across DB, API, WebSocket, and Client functions correctly.

Does a tracer bullet require complete error handling and full feature logic?

No, a tracer bullet requires only minimal error handling. It focuses on creating a thin vertical slice with clear traceability across all layers, serving as a planning tool to narrow scope and validate integration before widening the implementation.

What's the best way to plan a large feature spanning database, API, and client layers?

The best way to plan a large multi-layer feature is using a tracer bullet workflow. By building one thin vertical slice across DB, API, WebSocket, and Client, you validate real integration to narrow scope before widening the implementation.