documentation-architecture

Generate architecture documentation with frontmatter-driven structure, references, and risk tracking.

7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill documentation-architecture-kentoshimizu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: documentation-architecture
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/documentation-architecture
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill documentation-architecture-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Author architecture documentation that explains boundaries, dependencies, and operational constraints to reduce design/review ambiguity and improve decision traceability.

Core Features & Use Cases

  • Narrative capture of system boundaries and component dependencies to support architecture reviews.
  • Risk, constraint, and decision tracking using the provided templates and references.
  • Template-driven documentation suitable for ADRs and architecture governance across projects.

Quick Start

Create an architecture document for the target subsystem using the provided templates and assets.

Frequently Asked Questions about documentation-architecture

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

FAQPage Schema
How do I document system boundaries and dependencies for an architecture review?▼

To document system boundaries, this Skill automates architecture documentation by applying a frontmatter-driven structure that captures component relationships and operational constraints. It reduces design ambiguity and improves decision traceability across projects.

What is the best way to create an Architecture Decision Record with risk tracking?▼

Creating an Architecture Decision Record with risk tracking is best handled using this Skill's provided templates. It enforces a frontmatter-driven structure that documents open risks, constraints, and decisions, linking directly to references for traceability.

How do I use templates to enforce consistent architecture documentation across projects?▼

You can enforce consistent architecture documentation across projects by applying this Skill's frontmatter-driven structure. It links to provided references and assets to standardize how system boundaries, dependencies, and constraints are recorded.

Can I automate ADR creation and template-driven documentation updates?▼

Yes, you can automate ADR creation and template-driven documentation updates. This Skill applies automation to engineering decision-making tasks, ensuring boundary definitions and open risks are consistently captured and linked to provided references.

Does this approach require a specific format for documenting operational constraints?▼

Documenting operational constraints requires a frontmatter-driven structure format. This Skill enforces this specific format to ensure constraints, dependencies, and system boundaries are uniformly captured for architecture governance.