architecture-document-existing

Generate architecture documentation for an undocumented codebase by scanning structural signals like README files, package manifests, and entry points to infer project purpose and produce arc42-aligned docs under docs/architecture.

Arc42 documentation is a structured template for capturing software architecture context, decisions, and building blocks. Retrofit it during onboarding or major refactors when a codebase has partial structure but lacks formal architecture docs.

Detect architecture drift by comparing inferred code structure against design intent. The skill proposes retrofitting steps and logs unresolved unknowns in a 99-open-issues.md file for later investigation during refactors.

Inferring project purpose relies on scanning common code signals such as README files, package manifests, and application entry points. These artifacts provide the structural context needed to build an initial architecture overview.

Yes, this approach is designed for codebases that have some partial structure but lack formal architecture documentation. It works without dependencies and produces arc42-aligned docs plus an open-issues trail for unknowns.

Onboard developers by running the skill to infer architecture from code signals and generate arc42-aligned documentation under docs/architecture, providing a structured overview and an open-issues trail for unresolved unknowns.