legacy-brd-to-sdd-handoff

Name: legacy-brd-to-sdd-handoff
Availability: InStock
Author: wwa-lab

Validate and package Legacy BRD to SDD handoffs for forward SDLC compliance.

Updated May 12, 2026

Search Tags:#validation #handoff #spec #sdlc #brd

Ready to run

npx skills add https://github.com/wwa-lab/legacy-spec-factory --skill legacy-brd-to-sdd-handoff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: legacy-brd-to-sdd-handoff
Source: https://github.com/wwa-lab/legacy-spec-factory/tree/main/.opencode/skills/legacy-brd-to-sdd-handoff
Command: npx skills add https://github.com/wwa-lab/legacy-spec-factory --skill legacy-brd-to-sdd-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires legacy-spec-writer, legacy-ibmi-evidence-intake, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of validating and packaging a Legacy BRD to an SDD handoff, ensuring that all business and technical requirements are met and compliant with the forward SDLC.

Core Features & Use Cases

BRD Validation: Validates the status and sign-off of the BRD and spec.
Spec Validation: Validates the approval status and sign-off of the spec.
TBD Analysis: Analyzes and resolves blocking and non-blocking TBDs.
Acceptance Criteria: Ensures that all business rules have corresponding acceptance criteria.
Evidence Sensitivity: Validates the sensitivity and redaction status of evidence.
Traceability Matrix: Ensures the completeness of the traceability matrix.
Use Case: Imagine you have a Legacy BRD and spec ready for handoff. Use this Skill to automatically validate and package the handoff, ensuring that all requirements are met before it is consumed by the Atlas SDD chain.

Quick Start

Use the legacy-brd-to-sdd-handoff skill to validate and package the handoff for the capability 'Credit Limit Enforcement'.

Frequently Asked Questions about legacy-brd-to-sdd-handoff

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

FAQPage Schema

How do I validate a BRD for SDD handoff in the SDLC?▼

Validating a BRD for SDD handoff requires checking BRD and spec status, resolving blocking TBDs, verifying acceptance criteria for business rules, validating evidence sensitivity, and ensuring traceability matrix completeness before forward SDLC consumption.

What is BRD to SDD handoff validation and packaging?▼

BRD to SDD handoff validation is the process of verifying that business and technical requirements, evidence sensitivity, and traceability are fully compliant before packaging the handoff for consumption by the forward SDLC.

How do I ensure all business rules have acceptance criteria before spec handoff?▼

To ensure business rules have acceptance criteria before spec handoff, this validation skill automatically cross-references every documented business rule against the defined acceptance criteria to guarantee complete coverage and compliance.

Do I need access to the Legacy Spec Factory project to validate TBD resolutions?▼

Yes, you need access to the Legacy Spec Factory project and its relevant artifacts, because this skill performs TBD analysis and validates evidence redaction status directly against the dependencies legacy-spec-writer and legacy-ibmi-evidence-intake.

What is the best way to package a Legacy spec for the Atlas SDD chain?▼

The best way to package a Legacy spec for the Atlas SDD chain is to automate validation of BRD sign-off, TBD resolution, evidence sensitivity, and traceability matrix completeness to ensure full forward SDLC compliance before handoff.

Why does my BRD to SDD handoff fail compliance checks on blocking TBDs?▼

BRD to SDD handoff compliance checks fail on blocking TBDs because unresolved blocking items prevent forward SDLC consumption; this skill analyzes and resolves both blocking and non-blocking TBDs to clear the handoff package.