lld-docs

Generate backend and infrastructure LLD documents from PRDs, TRDs, and repository evidence.

3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill lld-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lld-docs
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/general/lld-docs
Command: npx skills add https://github.com/infraspecdev/tesseract --skill lld-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of authoring and maintaining structured Low-Level Design documents for backend and infrastructure work, keeping component-level architecture consistent and traceable.

Core Features & Use Cases

  • Drafting and merging LLDs: Creates new component-scoped LLDs or edits existing drafts without overwriting untouched sections.
  • Template-driven structure: Selects the correct backend or infra template and preserves the required 14-section canonical order with explicit anchors.
  • Operational safeguards: Uses atomic writes, Mermaid validation, provenance stamping, and changelog updates to keep documents reliable and auditable.

Quick Start

Ask the lld-docs skill to generate or update the LLD for the target component using the available PRD, TRD, and repository evidence.

Frequently Asked Questions about lld-docs

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

FAQPage Schema
How do I generate a low-level design document for a backend component from a PRD?

To generate a low-level design document, provide a PRD, TRD, or repository evidence to automatically draft a component-scoped LLD using a 14-section canonical structure with backend or infra template selection.

What is the canonical structure for a low-level design document?

The canonical structure for a low-level design document requires 14 specific sections with explicit anchors, ensuring component-level architecture remains consistent, traceable, and properly ordered for backend and infrastructure work.

How do I update an existing LLD draft without overwriting untouched sections?

To update an existing LLD draft without overwriting untouched sections, the tool merges canonical and draft LLDs under docs/lld and docs/shield feature paths while preserving the original 14-section structure and provenance.

Does the LLD generation process validate Mermaid diagrams and track changes?

Yes, LLD generation validates Mermaid diagrams and tracks changes through automated changelog updates, applying atomic writes and provenance stamping to keep infrastructure design documents reliable and auditable.

Can I use repository evidence to draft infrastructure design documents?

Yes, you can use repository evidence alongside PRDs and TRDs to draft infrastructure design documents, automatically selecting the correct infra template and applying the required 14-section canonical order with explicit anchors.