legacy-traceability-packager

Package end-to-end traceability into sealed audit bundles for legacy systems.

Updated May 12, 2026
One-click install
npx skills add https://github.com/wwa-lab/legacy-spec-factory --skill legacy-traceability-packager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legacy-traceability-packager
Source: https://github.com/wwa-lab/legacy-spec-factory/tree/main/.opencode/skills/legacy-traceability-packager
Command: npx skills add https://github.com/wwa-lab/legacy-spec-factory --skill legacy-traceability-packager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides end-to-end traceability packaging and audit for legacy systems, ensuring complete and accurate evidence and analysis coverage, while managing business rules, acceptance criteria, and decision-making processes.

Core Features & Use Cases

  • Traceability Packaging: Packages a capability's traceability into a sealed audit bundle for governance and review.
  • Evidence Analysis: Validates evidence manifest and program/flow/module analyses, ensuring every link in the chain is traceable and actionable.
  • Business Rule & Acceptance Criteria Handling: Ensures every business rule and acceptance criterion has supporting evidence and test coverage.
  • Decision Coverage: Tracks decision coverage, ensuring every decision is backed by business rules, behaviors, and constraints.
  • Use Case: Before an application retirement, this skill is used to ensure that every part of the application is traced back to its source and business rules are consistently applied.

Quick Start

Use the legacy-traceability-packager skill to package the traceability for capability 'CAPABILITY-SLUG'.

Frequently Asked Questions about legacy-traceability-packager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit end-to-end traceability for legacy systems before application retirement?

You audit end-to-end traceability for legacy systems by packaging evidence, business rules, and decision-making processes into a sealed bundle. This ensures complete coverage and integrity before retirement.

What is traceability packaging for legacy systems?

Traceability packaging for legacy systems consolidates evidence, business rules, and acceptance criteria into a sealed audit bundle. This ensures every component is fully traceable and auditable for governance review.

How do I ensure business rules and acceptance criteria have test coverage during legacy modernization?

To ensure business rules and acceptance criteria have test coverage, you validate the evidence manifest and program analyses. This verifies every rule and criterion has supporting evidence and linked test coverage.

Do I need upstream artefact approval to package legacy system traceability?

Yes, you need upstream artefact approval to package legacy system traceability. Operating within the Legacy Spec Factory framework requires approval of upstream artefacts and ensuring all references resolve or are explicitly blocked.

What limitations exist when tracking decision coverage for legacy application audit?

A key limitation when tracking decision coverage is that all references must resolve or be explicitly blocked. The process requires access to the evidence manifest, business rules, and decision-making artefacts to function correctly.

What's the best way to seal capability traceability for governance review?

The best way to seal capability traceability is to package it within the Legacy Spec Factory framework. This validates evidence, tracks decision coverage, and ensures all links are traceable for governance.