Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/ozten/skills/tree/main/tpm-spec-trace-ids
SKILL.md
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ozten/skills
five-whys
Root cause analysis technique for self-improvement. Use after any failure, mistake, or suboptimal outcome to find systemic causes and actionable changes. Triggers: analyzing why something went wrong, debugging repeated failures, post-mortem analysis, retrospectives, understanding root causes, reflecting on what could be improved.
ozten/skills
nano-banana-image-gen
Generate images using the `imagen` CLI (Gemini and OpenAI models). Use when the user says "nano banana", "generate an image", "create an image", "make me a picture", "image gen", "draw", "illustrate", or wants to create images from text prompts.
ozten/skills
webdev-combobox-autocomplete
Foundational patterns for building accessible autocomplete/combobox components with state management, ARIA patterns, keyboard navigation, async suggestions, and framework-agnostic implementation. Use when building autocomplete inputs, command palettes, search inputs, select replacements, or any dropdown with keyboard navigation and suggestions.
ozten/skills
ui-design-iteration
Iterates on data-intensive UI designs to improve scannability, hierarchy, accessibility, and systematization. Use when improving an existing UI, reviewing a design for UX issues, or transforming a functional-but-flat interface into a polished product.
ozten/skills
tpm-spec-verify
Enrich a Phase Sepc/PRD with Quality Requirements (Q-nnn) and Acceptance Criteria (AC-nnnn). Use when user wants to add QA perspective, define test criteria, identify non-functional requirements, add verification steps, or prepare a Phase PRD for test planning.
ozten/skills
find-bugs
Adversarial three-agent bug review pipeline. Runs search → adversary → judge to find high-confidence bugs with reduced false positives. Use: /find-bugs src/
Didn't find tool you were looking for?