Use when creating, drafting, or generating a new solution-approach page for quality.arc42.org — a file under approaches/ / .md. Triggers on requests like "write the X approach", "add an approach for X", or working through the approaches backlog in TODO/approaches/.
Use when creating, drafting, or generating a new standard page for quality.arc42.org — a file under standards/ / .md. Triggers on requests like "add the X standard", "write a standards page for X", or turning source notes in TODO/standards/ into a standard page.
Verifies the V-Model artifact graph: Epics, Features, ADRs, PLANs, Backlog, Wayfinder rows, code refs. Syntactic and semantic modes. Explicit user command for "consistency check", "graph check", "dead links", "orphan features", or before a release; routine enforcement runs via the pre-commit hook, not per phase.
Guides users through the V-Model workflow: takes stock of the project state, recommends the next phase skill, audits handoff state, and runs the Closing Handoff after a green security audit. Explicit user command for "where do I start", "what comes next", "wo bin ich gerade", "was kommt jetzt". Never for individual…
One entry point for repos that predate current DIA conventions: brownfield onboarding (existing codebase, legacy code, reverse engineer, we already have code) and legacy DIA upgrades (migrate v1/v2, upgrade DIA, FEATURE to FEAT, restructure backlog). Detects repo state, then runs a reverse walk, a script pass, or a…
Unified enterprise & software architecture skill grounded in four open-source standards — C4 + Structurizr DSL, ArchiMate 3.x, TOGAF ADM, and arc42 + ADRs (MADR). Use it whenever the user wants to: produce architecture diagrams as code (C4 context/container/component, Structurizr, PlantUML, Mermaid); write…
Final phase of DDS reverse-engineering. Synthesizes all per-module specs and global registries into the unified Arc42 specification tree (sections 01-12), producing a human-readable, citation-grounded specification of the legacy system suitable for understanding, audit, or driving a rewrite.
Phase 2 of DDS reverse-engineering. Performs deep, line-by-line excavation of a single module (or all modules) from a legacy codebase, extracting business rules, SQL queries, integrations, and dead code, with mandatory file:line citations and LLM-as-Judge fidelity verification on every claim.
Phase 1 of DDS reverse-engineering. Performs lightweight reconnaissance of a legacy codebase to detect the tech stack, enumerate entry points, build a module map, and estimate the cost of full excavation. Output is spec/00-survey.md.