playbooks

home / skills / ozten / skills / tpm-spec-trace-ids

tpm-spec-trace-ids skill

/tpm-spec-trace-ids

This skill annotates a vision PRD with Feature IDs and generates a Coverage Index to enable traceability and phased development.

npx playbooks add skill ozten/skills --skill tpm-spec-trace-ids

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.8 KB
---
name: tpm-spec-trace-ids
description: Annotate a Spec/PRD with Feature IDs and generate a Coverage Index. Use when user wants to add spec tags to a vision document, create F-nnn identifiers, set up traceability, or initialize a PRD framework for phased development.
---

# PRD Vision Annotator

Annotate a narrative vision document with traceable Feature IDs and generate a Coverage Index.

## Workflow

1. **Add Goals section** (if missing) — Extract or write 3-10 business objectives as G-01, G-02, etc.
2. **Assign Feature IDs** — Add `[F-nnn]` tags to major section headers
3. **Generate Coverage Index** — Create tracking file listing all features

## Step 1: Goals Section

If the vision PRD lacks explicit goals, add them at the top:

```markdown
## Goals

G-01: [Primary business objective]
G-02: [Secondary objective]
G-03: [Quality/compliance objective]
```

Extract goals from executive summary, introduction, or ask the user.

If the document contains goals already, add goal Ids and do not modify those pieces of prose.

## Step 2: Feature ID Assignment

Add Feature IDs to major section headers. Do not modify prose.

**Before:**
```markdown
## 14. RSVP Functionality

### 14.1 Process Flow
```

**After:**
```markdown
## 14. RSVP Functionality [F-014]

### 14.1 Process Flow
```

**Rules:**
- One Feature ID per major section (H2 level typically)
- Subsections inherit parent ID unless substantial enough for their own
- Number sequentially (F-001, F-002...) or match section numbers (§14 → F-014)
- Skip sections explicitly out of scope

## Step 3: Coverage Index

Generate a Coverage Index file using the template in `assets/coverage-index-template.md`.

List every Feature ID with initial status `Planned`.

## Reference

See `references/naming-conventions.md` for ID format details.

Overview

This skill annotates a product vision or PRD with traceable Feature IDs and produces a Coverage Index to track scope and status. It adds a Goals section when missing, tags major sections with F-nnn identifiers, and initializes a feature-level tracking file. The result is a lightweight traceability framework ready for phased development and test planning.

How this skill works

The skill scans the vision/PRD document for top-level sections and an executive summary to extract or create 3–10 goal statements labeled G-01, G-02, etc. It then assigns one Feature ID per major section (H2) by inserting [F-nnn] tags without altering prose, following sequential or section-number-based numbering. Finally, it generates a Coverage Index listing every Feature ID with an initial status of Planned for straightforward tracking.

When to use it

  • Initializing a PRD to prepare for phased delivery and traceability.
  • Adding machine-readable feature tags to a narrative vision or specification.
  • Creating a baseline Coverage Index for product planning or QA planning.
  • Preparing a document for downstream linking to tickets, tests, or release plans.
  • Standardizing identifiers across a large spec with many sections.

Best practices

  • Add a concise Goals section first (3–10 goals) to anchor feature mapping.
  • Tag only major sections with one Feature ID; let subsections inherit unless sizable.
  • Use sequential F-001 numbering or match existing section numbers for clarity.
  • Do not alter original prose when inserting IDs; keep annotations minimal and consistent.
  • Mark clearly any out-of-scope sections and skip assigning IDs to them.

Example use cases

  • Convert a narrative product vision into a traceable PRD before engineering kickoff.
  • Annotate a customer-facing requirements document so QA can generate test cases per F-nnn.
  • Create a Coverage Index to hand off to project managers for release planning.
  • Add Feature IDs to an existing spec to link features to JIRA tickets or issue trackers.
  • Prepare a phased delivery roadmap by grouping features and marking planned status.

FAQ

What numbering scheme should I use for Feature IDs?

Use sequential numbering (F-001, F-002…) for new docs or mirror section numbers (e.g., §14 → F-014) if that improves traceability.

Will this change my spec text?

No. The process only inserts Feature ID tags into major headers and adds a Goals section or Coverage Index; it does not modify existing prose.