create-architecture

Extract architectural requirements from PRDs into structured architecture documents.

1|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill create-architecture-acidicsoil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-architecture
Source: https://github.com/AcidicSoil/lms-llmsTxt/tree/main/.claude/skills/create-architecture
Command: npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill create-architecture-acidicsoil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically translates requirements into a comprehensive system architecture document (docs/architecture.md) with Architecture Decision Records (ADRs), non-functional requirements coverage, and technology stack justification.

Core Features & Use Cases

  • Document generation: Creates a complete architecture.md tailored to project type (Frontend, Backend, or Fullstack) with required sections.
  • ADR generation: Produces Architecture Decision Records with context, alternatives, and rationales.
  • Validation & templates: Applies standard templates from references and ensures required sections exist; exports a ready-to-ship artifact.

Quick Start

Provide a requirements file path and optional project type to generate the architecture package and save it to docs/architecture.md.

Frequently Asked Questions about create-architecture

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

FAQPage Schema
How do I generate architecture documentation from a requirements document?

To generate architecture documentation, provide a PRD or requirements file path to extract architectural needs and translate them into a structured architecture plan saved at docs/architecture.md.

How are Architecture Decision Records created from a PRD?

Architecture Decision Records are automatically generated from a PRD by computing a complexity score to determine the required ADR count, then producing records with context, alternatives, and rationales in docs/adrs/.

Can I auto-detect project type when creating an architecture document?

Yes, you can auto-detect project type when creating an architecture document; the system automatically identifies whether the project is Frontend, Backend, or Fullstack to tailor the required document sections.

What is non-functional requirements coverage in an architecture plan?

Non-functional requirements coverage in an architecture plan maps system constraints like scalability and performance, with the depth of NFR coverage automatically determined by the computed project complexity score.

How do I justify a technology stack in architecture documentation?

To justify a technology stack in architecture documentation, the system analyzes extracted requirements and generates a mapped technology stack justification alongside the main architecture document.

Does architecture document generation work for fullstack projects?

Yes, architecture document generation works for fullstack projects by automatically detecting the fullstack project type and applying standard templates to ensure all required architecture sections exist.