arc42-documentation
arc42 Architecture Documentation
Purpose
Generate complete, structured architecture documentation following the proven arc42 template (https://arc42.org/). The template provides 12 standardized sections covering all aspects of software architecture, from stakeholder requirements to technical implementation details.
When to Use This Skill
- Starting a new project that needs comprehensive architecture documentation
- Documenting existing systems that lack structured architecture descriptions
- Creating architecture overviews for stakeholders with different technical levels
- Preparing architecture documentation for certification (e.g., iSAQB)
- Establishing a consistent documentation standard across multiple projects
arc42 Template Overview
The arc42 template consists of 12 sections:
- Introduction and Goals - Requirements overview, quality goals, stakeholders
- Constraints - Technical and organizational limitations
- Context and Scope - System boundaries, external interfaces
More from oocx/tfplan2md
git-rebase-main
Safely rebase the current feature branch on top of the latest origin/main. Use when preparing a branch for PR, UAT, or release.
24website-quality-check
Run a lightweight, repeatable quality checklist for the website (including style guide adherence).
19analyze-chat-export
Export and analyze VS Code Copilot chat logs for retrospective metrics. Extracts model usage, tool invocations, approval patterns, and timing data.
18create-pr-azdo
Create an Azure DevOps pull request using az devops tooling; include the repo’s linear-history merge preference and ask the Maintainer if merge options differ.
17website-devtools
Use browser tools to inspect rendering and troubleshoot website issues with the Maintainer.
17agent-tool-selection
Guide for selecting appropriate VS Code Copilot tools when configuring agents, including environment-specific considerations.
17