kiro-spec-design-lld

Generate low-level design documents with interfaces, data models, and contracts from approved high-level designs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/scapia-oss/compass --skill kiro-spec-design-lld-scapia-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-design-lld
Source: https://github.com/scapia-oss/compass/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-spec-design-lld
Command: npx skills add https://github.com/scapia-oss/compass --skill kiro-spec-design-lld-scapia-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning an approved high-level design into precise, implementation-ready contracts is where specs quietly fail — un-idempotent calls, breaking interface changes, and unrepresentable states slip through. This Skill expands HLD components into detailed low-level design documents with adversarial contract critique before any code is written. ## Core Features & Use Cases - LLD Generation: Expands every HLD component into full detail blocks covering interfaces, data models, error handling, and testing strategy, written to design-lld.md. - Contract Critique Loop: Runs a code-grounded adversarial review that diffs each interface and error path against real callers, logging Q&A to design-qa-log.md and coverage to spec.json. - Lifecycle & Approval Gating: Validates HLD approval, respects workflow and artifact toggles (bugfix skip, LLD-only design-first), and updates spec metadata before task generation. - Use Case: After approving an HLD for a new notifications service, run the Skill to produce interface contracts, catch a non-idempotent retry path via the critique loop, and hand off an approved LLD for task breakdown. ## Quick Start Run /kiro-spec-design-lld my-feature to generate the low-level design for an approved HLD, adding -y to auto-approve the HLD gate for low-risk specs.

Frequently Asked Questions about kiro-spec-design-lld

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

FAQPage Schema
How do I generate a low-level design from an approved HLD?

Run /kiro-spec-design-lld <feature-name> after the HLD is approved. The Skill loads requirements, HLD, and steering context, drafts design-lld.md from the template, runs a contract critique loop, and finalizes the document after the review gate passes.

What is the contract critique loop in LLD generation?

The contract critique loop is an adversarial review that diffs each interface, data model, and error path against how real callers and downstream code behave. It asks one grounded question per turn, logs Q&A to design-qa-log.md, and records per-lens coverage in spec.json.

Can I generate an LLD without an approved HLD?

Only in two cases: pass -y to auto-approve the HLD for low-risk specs, or use a design-first workflow where the HLD artifact is disabled (LLD-only path). Otherwise the Skill stops and asks you to approve the HLD first.

Does the LLD phase run for bugfix specs?

No. When spec_type is bugfix, the design phase is skipped entirely and the Skill directs you to spec-tasks. It also self-skips when artifacts.design_lld is false in the spec lifecycle configuration.

Why does LLD generation stop with an HLD not approved error?

The Skill enforces HLD approval as a hard gate because LLD contracts must align with an agreed architecture. Approve design-hld.md first, or re-run with -y to auto-approve, then the LLD generation proceeds.