hld-reviewer

Analyze High-Level Design documents for PRD alignment and drift.

79|23|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/TestAny-io/testany-agent-skills --skill hld-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hld-reviewer
Source: https://github.com/TestAny-io/testany-agent-skills/tree/main/plugins/testany-eng/skills/hld-reviewer
Command: npx skills add https://github.com/TestAny-io/testany-agent-skills --skill hld-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineering teams verify that High-Level Design documents (HLD) align with the PRD and charter, preventing drift between planning and implementation. It simulates multi-actor design reviews to surface gaps, risks, and inconsistencies before code is written.

Core Features & Use Cases

  • PRD↔HLD drift detection: identifies omissions, expansions, misinterpretations, and boundary shifts between PRD and HLD.
  • Stage-based review: performs Phase 1 drift checks, Phase 2 technical review, and optional Phase 3 risk-driven perspectives based on project risk features.
  • Evidence-based reporting: outputs a structured findings document with actionable remediation and references to the exact PRD/HLD sections.

Quick Start

Run the hld-reviewer against an HLD document and its PRD baseline, for example:

  • Path: ./plugins/testany-eng/skills/hld-reviewer/references/drift-detection-guide.md (or your HLD file path)
  • Output: a categorized report detailing P0/P1/P2 issues, drift types, and suggested fixes.

Frequently Asked Questions about hld-reviewer

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

FAQPage Schema
How do I detect PRD and HLD drift in architecture design?

To detect PRD and HLD drift, analyze High-Level Design documents against PRD baselines to identify omissions, expansions, and boundary shifts. This process ensures planning and implementation alignment before code is written.

What is HLD drift detection and when do I need it?

HLD drift detection is the process of verifying High-Level Design alignment with PRD requirements. You need it for multi-team architecture reviews to surface gaps, risks, and inconsistencies before implementation begins.

How do I perform a risk-driven architecture review on an HLD document?

Perform a risk-driven architecture review by applying Phase 1 drift checks, Phase 2 technical reviews, and Phase 3 risk perspectives. This generates evidence-based conclusions with references to exact PRD and HLD sections.

Can I review multi-team project HLDs against a PRD baseline?

Yes, you can review multi-team project HLDs against a PRD baseline. The review simulates multi-actor design sessions to surface inconsistencies and outputs a structured findings document with P0/P1/P2 issues and suggested fixes.

What is the best way to prevent design drift before implementation?

The best way to prevent design drift is conducting robust HLD reviews that verify PRD alignment and detect boundary shifts. This simulates multi-actor design reviews to surface gaps and risks before code is written.