Document architectural constraints with rationales for arc42 Section 2.
npx skills add https://github.com/MSiccDev/arc42-toolkit --skill arc42-section-02
Please help me install this Agent Skill. Skill: arc42-section-02 Source: https://github.com/MSiccDev/arc42-toolkit/tree/main/skills/arc42-section-02 Command: npx skills add https://github.com/MSiccDev/arc42-toolkit --skill arc42-section-02
Architecture teams often struggle to capture, structure, and communicate the non-negotiable constraints that shape design decisions. This skill guides the creation of a clear, audit-ready Arc42 Section 2 document, ensuring constraints are categorized, justified, and aligned with other sections before architecture work proceeds.
Answer the guided questions with your project constraints to produce the Section 2 draft.
High-intent search queries and answers about installing and using this skill.
Architecture constraints are captured by identifying technical, organizational, regulatory, and conventions limitations that shape design decisions. This skill interactively prompts you to justify why each constraint is non-negotiable, generating a structured Arc42 Section 2 draft.
Non-negotiable architecture constraints are mandated languages, processes, compliance rules, and coding or API conventions that shape design decisions. You need to document them before architecture work proceeds to ensure boundary decisions are audited and aligned with your solution strategy.
Aligning Arc42 Section 2 constraints involves checking cross-section consistency with Section 4 (Solution Strategy) and Section 9 (Architecture Decisions). This skill prompts you during documentation to ensure constraints directly support your boundary decisions and overall design alignment.
Yes, you can generate LEAN, ESSENTIAL, or THOROUGH detail levels for your architecture constraints document. The skill supports iterative refinement across these detail levels until stakeholders are satisfied with the captured constraints and their rationales.
No, this architecture constraints skill operates without any dependencies. You can immediately start answering guided questions about your project constraints to produce an audit-ready Arc42 Section 2 draft.
JochenYangGenerate structured PRDs and user stories with acceptance criteria.
magnus919Document system context and constraints with arc42 mapped to Pyramid layers.
MSiccDevGenerate arc42 Section 3 context diagrams and interface tables.
MSiccDevAudit arc42 documentation for accuracy, completeness, and cross-section consistency.
