Detect cross-section ID inconsistencies in arc42 documentation.
npx skills add https://github.com/MSiccDev/arc42-toolkit --skill arc42-lint
Please help me install this Agent Skill. Skill: arc42-lint Source: https://github.com/MSiccDev/arc42-toolkit/tree/main/skills/arc42-lint Command: npx skills add https://github.com/MSiccDev/arc42-toolkit --skill arc42-lint
Keeps arc42 documentation consistent by validating cross-section references and ID mappings across the full template.
Run the arc42-lint tool to verify cross-section consistency across your architecture documentation.
High-intent search queries and answers about installing and using this skill.
To check arc42 documentation consistency, validate cross-section references like IF-xx, QS-xx, ADR, and RISK-xx IDs. This ensures interface IDs, deployment mappings, and quality goals remain aligned across all template sections.
Validate interface IDs by checking IF-xx references between Section 3 and Section 5. This cross-section linting ensures building block interfaces map correctly to deployment views without manual cross-referencing.
Arc42 linting works manually when automation is unavailable. Rules can be applied directly to verify Q42 tag traceability, ADR risk references, and aspirational scenario links without running the Python script.
The best way to trace Q42 tags is verifying their consistency between Section 1.2 and Section 10. This cross-section check ensures quality goals map directly to quality scenarios.
Verify ADR risk references by checking them against the Section 11 risk matrix. This ensures RISK-xx IDs in architecture decisions align with documented risks and aspirational scenarios in Section 10.3.
Manually apply arc42 linting rules when automation is unavailable or the Python script is absent. This allows validating cross-section ID mappings and interface consistency without script execution.
AndreaCadonnaGenerate CONTRACTS.md by formalizing SPEC.md requirements into invariants, boundary, security, and data integrity contracts.
MSiccDevGuide arc42 Section 1 documentation by capturing system purpose, quality goals, and stakeholders.
zzafergokConvert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.
bbvch-aiCreate, modify, and validate arc42-compliant software architecture documentation.
