speckit-arch-reverse

To generate 4+1 architecture views from an existing repository, this skill captures observable repository facts from file structures and configurations, then synthesizes scenario, logical, process, development, and physical views into a single source of truth.

Reverse engineering software architecture documentation is best handled by capturing repo evidence first, then synthesizing the 4+1 views to produce an architecture SSOT, avoiding manual reconstruction and ensuring alignment for onboarding teams.

Yes, you can update outdated architecture documentation by inspecting file structures, docs, and operational manifests as evidence, which refreshes the 4+1 views and explicitly reports missing evidence gaps instead of inventing unknown elements.

To locate output paths for architecture synthesis, you must run the repo-structure setup script first, which ensures the seven specified .specify/memory/* files are written correctly for the 4+1 views generation process.

Yes, reverse architecture generation works with missing configurations by enforcing evidence grounding and writing specific missing-evidence gaps into the facts and affected views, rather than fabricating unknown architecture elements.

Reverse architecture synthesis requires an evidence layer to support architecture conclusions with observable repository facts, preventing the views from becoming audit reports and ensuring the 4+1 architecture SSOT remains grounded.