requirements-traceability-manager
Design control traceability skill for managing user needs, design inputs, design outputs, and verification/validation linkages
Best use case
requirements-traceability-manager is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Design control traceability skill for managing user needs, design inputs, design outputs, and verification/validation linkages
Teams using requirements-traceability-manager should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/requirements-traceability-manager/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How requirements-traceability-manager Compares
| Feature / Agent | requirements-traceability-manager | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Design control traceability skill for managing user needs, design inputs, design outputs, and verification/validation linkages
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Requirements Traceability Manager Skill
## Purpose
The Requirements Traceability Manager Skill ensures comprehensive traceability throughout the medical device design control process, linking user needs to design inputs, design outputs, and verification/validation activities per 21 CFR 820.30.
## Capabilities
- Bidirectional traceability matrix generation
- Requirements coverage analysis
- Gap identification in V&V coverage
- Design change impact analysis
- Traceability report generation
- DHF (Design History File) completeness checking
- User needs to design input mapping
- Design output to verification linking
- Risk control to requirements tracing
- Regulatory requirement coverage tracking
- Orphan requirement identification
## Usage Guidelines
### When to Use
- Establishing design control traceability
- Conducting V&V coverage analysis
- Assessing design change impacts
- Preparing for regulatory audits
### Prerequisites
- User needs documented
- Design inputs established
- Design outputs defined
- V&V protocols available
### Best Practices
- Establish traceability from project inception
- Update matrices with every design change
- Verify bidirectional completeness regularly
- Integrate with requirements management tools
## Process Integration
This skill integrates with the following processes:
- Design Control Process Implementation
- Verification and Validation Test Planning
- Software Development Lifecycle (IEC 62304)
- Medical Device Risk Management (ISO 14971)
## Dependencies
- Requirements management tools (Jama Connect, Polarion, DOORS)
- Design documentation systems
- Test management platforms
- Change control systems
## Configuration
```yaml
requirements-traceability-manager:
traceability-levels:
- user-needs
- design-inputs
- design-outputs
- verification
- validation
- risk-controls
matrix-types:
- forward
- backward
- bidirectional
coverage-metrics:
- requirement-coverage
- test-coverage
- risk-coverage
```
## Output Artifacts
- Bidirectional traceability matrices
- Requirements coverage reports
- Gap analysis documents
- Impact assessment reports
- DHF completeness checklists
- Orphan requirement lists
- V&V coverage summaries
- Change impact analyses
## Quality Criteria
- Complete bidirectional traceability established
- All user needs traced to design inputs
- All design inputs traced to design outputs
- V&V activities cover all requirements
- Risk controls properly traced
- No orphan requirements existRelated Skills
plugin-registry-manager
Manage SDK plugin discovery and registration
deprecation-manager
Manage API and SDK deprecation lifecycle
api-key-manager
API key generation, rotation, and management system
zotero-reference-manager
Reference management for bibliography organization, annotation sync, and citation formatting
data-versioning-manager
Skill for managing data versions and provenance
nanosensor-calibration-manager
Nanosensor characterization skill for calibration, sensitivity analysis, and selectivity validation
nanomaterial-lims-manager
Laboratory Information Management System skill for nanomaterial sample tracking and data management
ligand-exchange-protocol-manager
Surface chemistry skill for managing ligand exchange reactions, bioconjugation protocols, and functional group quantification
cleanroom-protocol-manager
Cleanroom operations skill for managing protocols, contamination control, and process flows
requirements-flowdown
Skill for systematic requirements capture, decomposition, and traceability
computational-environment-manager
Manage reproducible computational environments
benchmark-suite-manager
Manage benchmarks for algorithm engineering experiments and evaluations