lld-reviewer

Review Low-Level Design documents against PRD, HLD, API contracts, and Guardrails.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure alignment between Low-Level Design (LLD) and upstream baselines (PRD/HLD/Contract/Guardrails) before implementation.

Core Features & Use Cases

  • Simulates LLD Review meetings to verify consistency with baselines, contracts, and guardrails.
  • Checks LLD Manifest completeness, coverage of guardrails, and evidence-backed conclusions to prevent drift.
  • Use Case: Before coding, run an LLD review to confirm interfaces, data models, and behavior align with PRD/HLD and API contracts.

Quick Start

Run the LLD review workflow against your LLD document and upstream baselines to produce a list of findings and recommended actions.

Frequently Asked Questions about lld-reviewer

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

FAQPage Schema
How do I ensure my LLD aligns with upstream PRD, HLD, and API contracts?

To ensure LLD alignment with upstream baselines, run an early design review that checks interface consistency, data models, and behavior against PRD, HLD, and API contracts before coding starts.

What is a gate-review assessment for low-level design?

A gate-review assessment for low-level design is an evidence-backed evaluation that decides if an LLD is ready for development by detecting missing references, contract inconsistencies, and baseline drift.

How do I check LLD manifest completeness and guardrail coverage?

You check LLD manifest completeness by simulating a design review meeting to verify that all guardrails are covered and that conclusions are evidence-backed to prevent baseline drift.

When do I need to run an LLD review against upstream baselines?

You need to run an LLD review against upstream baselines during early design stages before implementation, ensuring interfaces and behavior align with PRD, HLD, and API contracts to prevent coding drift.

Can I detect design drift and missing references before coding starts?

Yes, you can detect design drift and missing references before coding starts by applying an evidence-backed LLD review workflow that produces findings and recommended actions against upstream baselines.