How do I install the Tpm Spec Trace Ids skill?

Run npx skillmds@latest add tomevault-io/tpm-spec-trace-ids in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tpm Spec Trace Ids safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tpm Spec Trace Ids?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tpm Spec Trace Ids free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tpm Spec Trace Ids?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tpm Spec Trace Ids by tomevault-io — Agent Skill

Name: Tpm Spec Trace Ids
Author: tomevault-io

Tpm Spec Trace Ids

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. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

PRD Vision Annotator

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

Workflow

Add Goals section (if missing) — Extract or write 3-10 business objectives as G-01, G-02, etc.
Assign Feature IDs — Add [F-nnn] tags to major section headers
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.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: tpm-spec-trace-idsdescription: 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. Use when this capability is needed.---# PRD Vision AnnotatorAnnotate a narrative vision document with traceable Feature IDs and generate a Coverage Index.## Workflow1. **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 headers3. **Generate Coverage Index** — Create tracking file listing all features## Step 1: Goals SectionIf the vision PRD lacks explicit goals, add them at the top:```markdown## GoalsG-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 AssignmentAdd 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 IndexGenerate a Coverage Index file using the template in `assets/coverage-index-template.md`.List every Feature ID with initial status `Planned`.## ReferenceSee `references/naming-conventions.md` for ID format details.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/ozten) — claim your Tome and manage your conversions.

Frequently asked questions