prd-tracers

Convert a PRD into phased tracer bullets with demos and executable tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert a PRD into phased tracer bullets with demos and executable tasks to enable end-to-end delivery planning.

Core Features & Use Cases

  • Phase-based tracer generation from a PRD, including demos and atomic tasks.
  • Automatic creation of PROGRESS.md and state.json to track progress and status.
  • Structured, testable task verification steps to ensure traceability from PRD to implementation.

Quick Start

Generate a phased tracer plan for the PRD located at docs/prd/<feature-slug>/PRD.md.

Frequently Asked Questions about prd-tracers

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

FAQPage Schema
How do I convert a PRD into phased tracer bullets with executable tasks?

Generating a phased tracer plan from a PRD requires the document to exist at docs/prd/<feature-slug>/PRD.md. The Skill processes this file to produce tracer bullets, demos, and executable tasks automatically.

What is a phased tracer plan in product delivery planning?

A phased tracer plan breaks down a PRD into sequential tracer bullets spanning multiple phases, each containing demos and atomic tasks with structured testable verification steps to ensure traceability from requirements to implementation.

How do I track progress and status for a generated tracer plan?

Progress and status for a generated tracer plan are tracked through automatically created PROGRESS.md and state.json files, which contain tracer definitions, demos, and verifications to maintain delivery visibility.

Does the tracer generation require any external dependencies or components?

Tracer generation requires no external dependencies or components. It operates independently to parse the PRD document and output the phased tracers, demos, and status tracking files.

Can I use this for task decomposition across multiple delivery phases?

Yes, this is designed for task decomposition across multiple phases. It takes an existing PRD and breaks it down into atomic, executable tasks and demos organized within a phased end-to-end tracer plan.