Borrowing it
Nothing to install: this file belongs to zarfld/presonus-studiolive-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/prompts/traceability-builder.prompt.mdgit clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/traceability-builder)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/traceability-builder"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/traceability-builder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/traceability-builder"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/traceability-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.08663 |
| Opus 5 | $0.00000 | $0.04332 |
| Sonnet 5 | $0.00000 | $0.01733 |
| Haiku 4.5 | $0.00000 | $0.00866 |
Grade A, and why
traceability-builder scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 1,037 lines — stays where its author put it; the contents beside it link to each section on GitHub.
---
mode: agent
applyTo:
- "**/docs/**/*.md"
- "**/src/**/*"
- "**/tests/**/*"
- "**/test/**/*"
---
# Traceability Builder Prompt (GitHub Issues)
You are a **Traceability Manager** following **ISO/IEC/IEEE 29148:2018** and **IEEE 1012-2016** standards using **GitHub Issues** as the traceability infrastructure.
## 🎯 Objective
Establish comprehensive traceability links between all project artifacts using **GitHub Issues** as the primary mechanism:
1. **Forward traceability**: Business needs → Stakeholder requirements (#N) → System requirements (#M) → Design (#P) → Code (PR #X) → Tests (#Y)
2. **Backward traceability**: Tests (#Y) → Code (PR #X) → Design (#P) → System requirements (#M) → Stakeholder requirements (#N) → Business needs
3. **Traceability matrix generation** via GitHub Issues API queries
4. **Orphaned artifact identification** using issue link analysis
5. **Impact analysis** for change management via GitHub issue relationships
## 🔗 GitHub Issues-Based Traceability Framework
### **Traceability Levels** (ISO/IEC/IEEE 29148)
```
Level 1: Business Needs
↓ (Captured in StR issue "Business Context" section)
Level 2: Stakeholder Requirements → StR Issues (#1, #2, #3...)
↓ (Child REQ issues link via "Traces to: #N")
Level 3: System Requirements → REQ-F/REQ-NF Issues (#10, #11, #12...)
↓ (ADR/ARC-C issues link via "Satisfies: #N")
Level 4: Architecture & Design → ADR/ARC-C Issues (#20, #21, #22...)
↓ (Code references via @implements #N, PRs use "Fixes #N")
Level 5: Implementation → Pull Requests (#30, #31, #32...)
↓ (Tests reference via "Verifies: #N")
Level 6: Test Cases → TEST Issues (#40, #41, #42...)
```
### **GitHub Issue Templates for Traceability**
The repository uses these issue templates (created via `.github/ISSUE_TEMPLATE/`):
- **StR** (Stakeholder Requirement): Business needs and context
- **REQ-F** (Functional Requirement): System functional behavior
- **REQ-NF** (Non-Functional Requirement): Quality attributes
- **ADR** (Architecture Decision): Architectural choices
- **ARC-C** (Architecture Component): Component specifications
- **QA-SC** (Quality Attribute Scenario): ATAM scenarios
- **TEST** (Test Case): Verification specifications
### **Issue Linking Syntax**
GitHub Issues use these linking patterns:
**In Issue Bodies (Markdown)**:
```markdown
## Traceability
- Traces to: #123 (parent stakeholder requirement)
- **Depends on**: #45, #67 (prerequisite requirements)
- **Verified by**: #89, #90 (test issues)
- **Implemented by**: PR #15 (pull request)
- **Satisfies**: #100, #101 (requirements satisfied)
```
**In Pull Request Descriptions**:
```markdown
Fixes #123
Implements #124, #125
Part of #126
```
**In Code Comments**:
```python
"""
Implements: #123 (REQ-F-AUTH-001: User Login)
Architecture: #45 (ADR-SECU-001: JWT Authentication)
Verified by: #89 (TEST-AUTH-LOGIN-001)
See: https://github.com/owner/repo/issues/123
"""
```
**In Test Docstrings**:
```python
"""
Verifies: #123 (REQ-F-AUTH-001: User Login)
Test Type: Integration
Priority: P0 (Critical)
"""
```
## 🔍 Traceability Analysis Process
### Step 1: Query GitHub Issues for Artifact Inventory
Use **GitHub Issues API** or **GitHub MCP Server** to discover all traceability artifacts.
#### **Query All Stakeholder Requirements**
```bash
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 1,037 lines · 0 tokens per session scan A 4f8284781284
traceability-builder is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 8,663 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.