agentleFS
oztenozten/skills/tpm-spec-trace-ids/SKILL.md

tpm-spec-trace-ids

Skill7 starsChanged 9 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 18
  2. Distinctive:

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

    line 30
  3. Distinctive:

    Add Feature IDs to major section headers.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

## 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:

## 14. RSVP Functionality

### 14.1 Process Flow

After:

## 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.