legacy-golden-master-test-planner

Generate golden master test plans from approved specifications and runtime evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps plan golden master equivalence tests for modernizing legacy systems, ensuring that new implementations accurately replicate legacy behavior.

Core Features & Use Cases

  • Test Plan Generation: Automatically create a comprehensive test plan from approved specifications and runtime evidence.
  • Equivalence Coverage: Ensure that all critical business rules and acceptance criteria are covered by the test plan.
  • Runtime Evidence Integration: Incorporate redacted runtime evidence into the test plan for accurate validation.
  • Use Case: For a legacy credit limit enforcement system, this Skill can generate a test plan that covers all scenarios, including normal operations, credit limit exceeded, and boundary conditions.

Quick Start

Use the legacy-golden-master-test-planner skill to generate a test plan for the 'credit-limit-enforcement' capability.

Frequently Asked Questions about legacy-golden-master-test-planner

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

FAQPage Schema
How do I plan golden master equivalence tests for legacy system modernization?

Golden master equivalence testing is a technique that validates legacy modernization by comparing new implementation outputs against recorded legacy system behavior. It generates a test plan from approved specifications and redacted runtime evidence to ensure accurate behavioral replication.

How do I integrate runtime evidence into a legacy test plan?

You integrate runtime evidence by incorporating redacted runtime data into the test plan generation process. This validates that the test coverage accurately reflects actual legacy system operations, including normal processing, boundary conditions, and exception scenarios.

Can I use specification analysis to cover boundary conditions in legacy modernization?

Yes, specification analysis extracts all business rules and acceptance criteria from approved documents to generate test coverage. This guarantees that boundary conditions, such as credit limit exceeded scenarios, are explicitly validated in the modernization test plan.

What is the best way to ensure equivalence coverage for a legacy credit limit enforcement system?

The best way to ensure equivalence coverage is generating an automated test plan that targets normal operations, credit limit exceeded states, and boundary conditions. This approach guarantees all critical business rules are validated during the legacy modernization process.

Does golden master testing work without approved specifications for legacy modernization?

Golden master testing relies on approved specifications to ensure comprehensive coverage of business rules and acceptance criteria. Without specifications, generating a test plan that accurately validates all critical legacy behaviors and boundary conditions is significantly compromised.