How do I install the Architecture Design skill?

Run npx skillmds@latest add ksmyl/architecture-design in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Architecture Design safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Architecture Design?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Architecture Design free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Architecture Design?

ksmyl (@ksmyl) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Architecture Design by ksmyl — Agent Skill

Name: Architecture Design
Author: ksmyl

Architecture Design

How to create ASPICE-compliant system and software architecture documents. Use this skill when designing system architecture (SYS.3), software architecture (SWE.2), or detailed design (SWE.3). Also use when allocating requirements to architectural elements, defining interfaces, describing dynamic behaviour with Mermaid diagrams, evaluating alternative architectures, defining resource consumption objectives, or creating Doorstop SYSARCH/SWARCH/SWDD traceability items. Consult this whenever you see WP 04-06 (system arch), WP 04-04 (SW arch), or WP 04-05 (detailed design).

ksmyl d6c75a2 3 files · 5.9 KB Updated Sep 17, 2026

File contents

Architecture and Design for ASPICE

Architecture Documents vs Doorstop Items

ASPICE architecture work products (WP 04-06, 04-04, 04-05) are documents — coherent descriptions with diagrams, rationale, and narrative. They live in artifacts/WP_04-06_*.md, artifacts/WP_04-04_*.md, artifacts/WP_04-05_*.md.

Doorstop items (SYSARCH, SWARCH, SWDD) are traceability anchors — lightweight entries that enable Doorstop's automated link-checking to verify requirement->architecture->design->code chains. Each Doorstop item should contain a brief description and reference the corresponding section of the architecture document.

The real architecture is the Markdown WP. The Doorstop item is an index entry that makes the architecture traceable.

Required Sections (Summary)

All architecture documents must include:

Context and boundaries (Mermaid context diagram)
Architectural elements table with stable IDs
Requirement allocation matrix
Interface definitions (protocols, data formats, timing)
Dynamic behaviour (sequence/state diagrams)
Alternative evaluation (at least one alternative with rationale)
Traceability and consistency statement

WP 04-04 (SW arch) adds: resource consumption objectives, layering. WP 04-05 (detailed design) adds: per-component algorithms, unit interfaces, code mapping via unit_file.

Detailed References

For detailed required sections for WP 04-06, 04-04, and 04-05 including Doorstop item examples, read references/architecture-sections.md.
For Mermaid diagram guidance, alternatives evaluation template, and technology adaptation table, read references/patterns.md.

---name: architecture-designdescription: How to create ASPICE-compliant system and software architecture documents. Use this skill when designing system architecture (SYS.3), software architecture (SWE.2), or detailed design (SWE.3). Also use when allocating requirements to architectural elements, defining interfaces, describing dynamic behaviour with Mermaid diagrams, evaluating alternative architectures, defining resource consumption objectives, or creating Doorstop SYSARCH/SWARCH/SWDD traceability items. Consult this whenever you see WP 04-06 (system arch), WP 04-04 (SW arch), or WP 04-05 (detailed design).---# Architecture and Design for ASPICE## Architecture Documents vs Doorstop ItemsASPICE architecture work products (WP 04-06, 04-04, 04-05) are **documents** — coherent descriptions with diagrams, rationale, and narrative. They live in `artifacts/WP_04-06_*.md`, `artifacts/WP_04-04_*.md`, `artifacts/WP_04-05_*.md`.Doorstop items (SYSARCH, SWARCH, SWDD) are **traceability anchors** — lightweight entries that enable Doorstop's automated link-checking to verify requirement->architecture->design->code chains. Each Doorstop item should contain a brief description and reference the corresponding section of the architecture document.The real architecture is the Markdown WP. The Doorstop item is an index entry that makes the architecture traceable.## Required Sections (Summary)All architecture documents must include:1. Context and boundaries (Mermaid context diagram)2. Architectural elements table with stable IDs3. Requirement allocation matrix4. Interface definitions (protocols, data formats, timing)5. Dynamic behaviour (sequence/state diagrams)6. Alternative evaluation (at least one alternative with rationale)7. Traceability and consistency statement**WP 04-04 (SW arch)** adds: resource consumption objectives, layering.**WP 04-05 (detailed design)** adds: per-component algorithms, unit interfaces, code mapping via `unit_file`.## Detailed References- For detailed required sections for WP 04-06, 04-04, and 04-05 including Doorstop item examples, read `references/architecture-sections.md`.- For Mermaid diagram guidance, alternatives evaluation template, and technology adaptation table, read `references/patterns.md`.

Frequently asked questions