arc42-section-01

Guide arc42 Section 1 documentation by capturing system purpose, quality goals, and stakeholders.

20|3|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/MSiccDev/arc42-toolkit --skill arc42-section-01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arc42-section-01
Source: https://github.com/MSiccDev/arc42-toolkit/tree/main/skills/arc42-section-01
Command: npx skills add https://github.com/MSiccDev/arc42-toolkit --skill arc42-section-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Arc42 Section 1 skill guides teams to capture the system purpose, essential quality goals, and stakeholders before producing the architecture draft.

Core Features & Use Cases

  • Interactive questioning to gather system name, goals, stakeholders, and requirements.
  • Enforces mandatory quality goals (Section 1.2) before any architectural drafting begins.
  • Generates a structured Section 1 draft with multiple detail levels (LEAN, ESSENTIAL, THOROUGH) and iterative refinement based on user feedback.
  • Supports traceability to related arc42 sections and reference material.

Quick Start

Answer the guided questions to collect system details, quality goals, and stakeholders, then generate Section 1 draft.

Frequently Asked Questions about arc42-section-01

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

FAQPage Schema
How do I document stakeholders and quality goals for arc42 architecture documentation?

To document stakeholders and quality goals for arc42 architecture documentation, you can use an interactive guide that asks targeted questions to capture system purpose, stakeholder sign-off information, and mandatory Section 1.2 quality goals before drafting.

What is the best way to start arc42 Section 1 for a new software project?

The best way to start arc42 Section 1 is by answering guided questions to collect system details, essential quality goals, and stakeholder requirements, which then generates a structured draft aligned with arc42 standards.

Can I generate arc42 documentation drafts at different detail levels?

You can generate arc42 documentation drafts at LEAN, ESSENTIAL, or THOROUGH detail levels, allowing iterative refinement and flexible architecture documentation based on your project requirements.

Why are quality goals mandatory before drafting architecture in arc42?

Quality goals are mandatory before drafting architecture in arc42 because Section 1.2 enforces capturing essential quality requirements early to ensure the architecture design aligns with stakeholder needs and system purpose.

How do I capture stakeholder sign-off during early architecture work?

You capture stakeholder sign-off during early architecture work by answering targeted interactive questions that surface stakeholder details and requirements, integrating them directly into the Section 1 draft generation process.