skills.rest
wwa-lab
wwa-labOFFICIAL
Explore all skills by this author →
GitHub

legacy-brd-writer

Synthesize business requirements documents from legacy module analysis evidence.

Updated May 12, 2026
Search Tags:#analysis#migration#BRD#business requirements#legacy system
One-click install
npx skills add https://github.com/wwa-lab/legacy-spec-factory --skill legacy-brd-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: legacy-brd-writer
Source: https://github.com/wwa-lab/legacy-spec-factory/tree/main/.opencode/skills/legacy-brd-writer
Command: npx skills add https://github.com/wwa-lab/legacy-spec-factory --skill legacy-brd-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires module-overview, program-analysis, flow-analysis, object-map, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill turns legacy analysis evidence into a stakeholder-readable Business Requirements Document (BRD) for migration discovery and SME review, facilitating the understanding and documentation of legacy systems.

Core Features & Use Cases

  • Evidence-backed BRD Creation: Translates analysis evidence into a stakeholder-readable BRD.
  • Module Analysis Integration: Requires approved module analysis for input.
  • Business Process Synthesis: Creates a business narrative in SME language without technical jargon.
  • Validation and Scenario Generation: Includes validation scenarios for review.

Quick Start

Use the legacy-brd-writer skill to generate a BRD for the approved order-entry module analysis.

Frequently Asked Questions about legacy-brd-writer

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

FAQPage Schema
How do I create a business requirements document for a legacy system migration?▼

You can generate a business requirements document for legacy system migration by synthesizing approved module analysis evidence into a BRD focusing on observed behaviors, inferred rules, and validation scenarios.

What is evidence-backed BRD creation for legacy systems?▼

Evidence-backed BRD creation translates legacy system analysis evidence, such as module overviews and flow analysis, into a business narrative using SME language without technical jargon for stakeholder review.

How do I translate legacy system analysis into business requirements?▼

Translate legacy system analysis into business requirements by synthesizing module analysis evidence into a BRD that captures observed behaviors, inferred rules, gaps, and validation scenarios for SME review.

Do I need approved module analysis to generate a legacy system BRD?▼

Yes, generating a legacy system BRD requires approved module analysis evidence as input to ensure the resulting business requirements document accurately reflects observed behaviors and inferred rules.

Can I generate validation scenarios for legacy system migration review?▼

Yes, you can generate validation scenarios for legacy system migration review by synthesizing module analysis evidence into a BRD that includes validation scenarios specifically designed for stakeholder evaluation.

Related Skills

Explore More Product & Management Skills→
wwa-labwwa-lab

legacy-modernization-orchestrator

Guide IBM i/AS400 modernization through Legacy Spec Factory workflow stages.

Official
Advanced
wwa-labwwa-lab

legacy-sme-review-facilitator

Facilitate structured SME reviews and capture decisions for Legacy Spec Factory artifacts.

Official
Advanced
zinohomezinohome
1

codebase-summarizer

Scan repository structure and generate ARCHITECTURE.md documentation with system overview and module relationships.

Community
Advanced
neo-unicornneo-unicorn
2

dbs-deconstruct

Deconstruct ambiguous business concepts into atomic components using a seven-table ontological framework.

Community
Intermediate