kiro-spec-design-hld

Generate high-level architecture design documents for approved feature specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Turning approved requirements into a sound system architecture is error-prone: designs often ignore how the codebase actually works, miss failure paths, or skip requirements traceability. This Skill produces a grounded high-level design (HLD) document that is critiqued against the real code before it is finalized. ## Core Features & Use Cases - Architecture Generation: Produces a design-hld.md covering architecture, system flows, change surface, requirements traceability, and a component summary, following a strict template. - Code-Grounded Critique Loop: Runs an architect critique dialogue that diffs the proposed design against actual codebase behavior, covering contracts, blast radius, consistency, and failure paths. - Discovery & Research Logging: Classifies the change (new feature, extension, simple addition) and persists findings, codebase grounding evidence, and assumptions to research.md. - Use Case: After approving requirements for a notifications feature, run the Skill to get an HLD that maps every requirement to components, flags risky integration points, and records design decisions for the downstream low-level design phase. ## Quick Start Ask the AI to generate the high-level design for your feature by running the kiro-spec-design-hld skill with your feature name after its requirements are approved.

Frequently Asked Questions about kiro-spec-design-hld

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

FAQPage Schema
How do I generate a high-level design document from requirements?

Run the Skill with your feature name after requirements are approved. It loads the spec, steering context, and templates, runs discovery and an architecture critique loop, then writes design-hld.md with architecture, flows, and traceability.

What is the difference between HLD and LLD in spec-driven development?

The HLD covers architecture, system boundaries, change surface, and a component summary table. It deliberately excludes detailed interfaces, data models, error handling, and testing strategy, which belong to the low-level design phase that follows.

Can I generate a design without approved requirements?

Only in two cases: pass the -y flag to auto-approve requirements, or use a design-first workflow where project description and steering context are accepted as sufficient input. Otherwise the Skill stops until requirements are approved.

Does the design skill work for bugfix specifications?

Yes. For bugfix specs it uses bugfix.md (Current/Expected/Unchanged behavior) as the requirement contract instead of requirements.md, and skips the numeric requirement-ID validation. Complex bugfixes with design enabled get the full critique loop.

Why does the skill ask architecture questions before writing the design?

The architect critique loop diffs the proposed design against how the codebase actually works, surfacing failure paths, blast radius, and consistency gaps before the design is frozen. Answers are logged to design-qa-log.md for downstream phases.