Menú
Traces requirements through Jama's relationship graph — upstream to stakeholder needs, downstream to test cases and design items.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Demo pipeline state machine — 7-phase autonomous sequence with delegation context templates, phase transition logic, BLOCKED recovery strategies, and demo-state.json schema. Used exclusively by demo-conductor.
Cinematic narration style guide for demo-conductor — ANSI-coloured banner formats, live pipeline scoreboard, audience-facing language, phase summaries, and error narration patterns. Keeps the demo presentation-quality throughout.
Standardized completion and escalation protocol for subagent responses. Ensures the conductor can machine-parse every subagent return. Use when reporting completion status back to the orchestrator.
Cross-session learnings lifecycle — schema, storage, retrieval, and pruning of lessons learned during orchestrator sessions. Use when managing learnings via the /learn command.
Agent Teams assembly and task injection — selects appropriate team, validates prerequisites, estimates cost, injects tasks into the shared task list, and manages team lifecycle.
Token and cost tracking with model tier enforcement
| name | req-tracing |
| description | Traces requirements through Jama's relationship graph — upstream to stakeholder needs, downstream to test cases and design items. |
During planning or review phases when you need to understand the full traceability chain for a requirement, feature, or test case.
## Traceability Report: {item_name} ({document_key})
### Upstream (traces to)
| Item | Type | Name | Status |
|------|------|------|--------|
| REQ-123 | Stakeholder Need | User authentication | Approved |
### Downstream (traced from)
| Item | Type | Name | Status |
|------|------|------|--------|
| TC-456 | Test Case | Login flow test | Active |
| DES-789 | Design Element | Auth module design | Draft |
### Coverage Summary
- Upstream requirements: {count} ({covered}% with approved status)
- Test coverage: {count} test cases ({passed}% passing)
- Gaps: {items without downstream test coverage}
# Trace a requirement
claude -p "trace requirement item 1234 in Jama — show upstream needs and downstream test cases" \
--tool mcp__cc_jama__get_item --tool mcp__cc_jama__get_relationships
# Find untested requirements
claude -p "find all requirements in Jama project 5 that have no downstream test case relationships" \
--tool mcp__cc_jama__get_items --tool mcp__cc_jama__get_relationships