skill-arch-write-hld

Generate a structured High-Level Design document covering architecture, deployment, security, and integration points.

4|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill skill-arch-write-hld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-arch-write-hld
Source: https://github.com/ryan-nguyen-01/agent-platform/tree/main/.claude/skills/skill-arch-write-hld
Command: npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill skill-arch-write-hld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineers and architects produce a complete High-Level Design (HLD) document that captures system overview, architecture, components, deployment view, security considerations, scalability, and integration points for a project.

Core Features & Use Cases

  • Structured HLD template covering system overview, architecture, deployment, security, and integration points.
  • Includes guidelines for diagrams, component responsibilities, data flows, and security modeling to support architecture reviews.
  • Reusable for project handoffs, onboarding, and stakeholder alignment across development teams.

Quick Start

Provide a project name and a brief requirements summary, then run the skill to generate docs/hld.md ready for review.

Frequently Asked Questions about skill-arch-write-hld

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

FAQPage Schema
How do I generate a high-level design document for system architecture review?

Generate a high-level design document by applying this skill to a project brief or ADR, which structures system overview, architecture, deployment, security, and integration points into a review-ready file. It outputs a structured markdown file capturing diagrams, data flows, and component responsibilities.

What should a high-level design document include for stakeholder alignment?

A high-level design document for stakeholder alignment should include a system overview, architecture diagrams, component responsibilities, data flows, deployment views, security considerations, and integration points. This structure supports stakeholder discussions, developer onboarding, and project handoffs.

Can I use this skill to create an HLD for a microservices architecture?

Yes, you can use this skill to create an HLD for a microservices architecture. It supports generating design documents across monoliths, microservices, and modular architectures, capturing component responsibilities, deployment views, and integration points specific to distributed systems.

How do I document deployment views and security considerations in a design document?

Document deployment views and security considerations by running this skill on your project requirements. It automatically structures these elements into the generated design document, applying guidelines for security modeling and deployment architecture to ensure comprehensive coverage.

Does this skill work with existing architecture decision records for developer handoffs?

Yes, this skill works with existing architecture decision records for developer handoffs. Apply it directly to your ADRs or project briefs to generate a complete design document that captures system overview, architecture, and integration points for team alignment.