musubix-traceability

Guide for managing traceability between requirements, designs, code, and tests. Use this when asked to verify traceability, create traceability matrices, or perform impact analysis.

⭐5stars🔀0forks📁View on GitHub🕐Updated Jan 8, 2026⬇️2downloads

When & Why to Use This Skill

The MUSUBIX Traceability skill is a professional-grade tool designed to manage and verify bidirectional traceability throughout the software development lifecycle (SDLC). It bridges the gap between requirements, design specifications, implementation tasks, source code, and test suites. By automating the creation of traceability matrices and providing robust impact analysis, this skill ensures that every requirement is accounted for, tested, and documented, significantly improving software quality and simplifying compliance auditing.

Use Cases

  • Compliance Auditing: Automatically generate comprehensive traceability matrices to satisfy regulatory requirements and industry standards by proving that all requirements are implemented and verified.
  • Change Impact Analysis: Determine the exact scope of work when a requirement changes by identifying all linked designs, code modules, and test cases that need updating.
  • Gap Analysis and Coverage Verification: Use automated validation tools to find 'orphaned' requirements or untested code, ensuring 100% test coverage and requirement fulfillment.
  • Technical Documentation: Maintain a living link between business logic and technical implementation by embedding traceability metadata directly into code comments and test files.
namemusubix-traceability
descriptionGuide for managing traceability between requirements, designs, code, and tests. Use this when asked to verify traceability, create traceability matrices, or perform impact analysis.
licenseMIT

MUSUBIX Traceability Skill

This skill guides you through maintaining full traceability across the development lifecycle.

Overview

MUSUBIX enforces Article V - Traceability: Complete bidirectional tracing between:

Requirements (REQ-*) ↔ Design (DES-*) ↔ Tasks (TSK-*) ↔ Code ↔ Tests

Traceability Matrix

Creating a Traceability Matrix

# Traceability Matrix

| 要件ID | 設計ID | タスクID | コード | テスト |
|--------|--------|---------|--------|--------|
| REQ-AUTH-001 | DES-AUTH-001 | TSK-001 | src/auth/auth-service.ts | auth.test.ts |
| REQ-AUTH-002 | DES-AUTH-001 | TSK-002 | src/auth/token-manager.ts | token.test.ts |

CLI Commands

# Generate traceability matrix
npx musubix trace matrix

# Impact analysis for a specific requirement
npx musubix trace impact REQ-AUTH-001

# Validate all traceability links
npx musubix trace validate

Traceability in Code

Adding Traceability Comments

/**
 * AuthService - 認証サービス
 * @requirement REQ-AUTH-001
 * @design DES-AUTH-001
 * @task TSK-001
 */
export class AuthService {
  /**
   * ユーザー認証
   * @requirement REQ-AUTH-001
   */
  async authenticate(credentials: Credentials): Promise<Result<Token, AuthError>> {
    // Implementation
  }
}

Test Traceability

/**
 * @requirement REQ-AUTH-001
 * @design DES-AUTH-001
 */
describe('AuthService', () => {
  describe('authenticate', () => {
    it('should return token for valid credentials', async () => {
      // Test implementation
    });
  });
});

Impact Analysis

When a requirement changes, identify all affected artifacts:

flowchart LR
    REQ[REQ-AUTH-001<br/>変更] --> DES[DES-AUTH-001<br/>設計]
    DES --> TSK1[TSK-001<br/>タスク]
    DES --> TSK2[TSK-002<br/>タスク]
    TSK1 --> CODE1[auth-service.ts]
    TSK2 --> CODE2[token-manager.ts]
    CODE1 --> TEST1[auth.test.ts]
    CODE2 --> TEST2[token.test.ts]

Impact Analysis Steps

  1. Identify changed requirement (REQ-*)
  2. Find linked designs (DES-*)
  3. Find linked tasks (TSK-*)
  4. Locate affected code files
  5. Identify tests to update
  6. Update all artifacts

Traceability Storage

storage/traceability/
├── matrix.json           # Full traceability matrix
├── requirements-map.json # REQ -> DES mappings
├── design-map.json       # DES -> TSK mappings
└── code-map.json         # TSK -> Code mappings

Verification Checklist

Before completing any feature:

  • All requirements have linked designs
  • All designs have linked tasks
  • All tasks have linked code
  • All code has linked tests
  • Traceability comments in code
  • Matrix updated

MCP Tool

Use MCP tool for automated validation:

Tool: sdd_validate_traceability
Description: Validates bidirectional traceability across all artifacts
  • musubix-sdd-workflow - Full SDD workflow
  • musubix-ears-validation - Requirements validation
  • musubix-test-generation - Generate tests with traceability