ln-72-current-architecture-documenter

Run this Skill against the checked-out repository to map modules, services, data stores, and deployment units from actual code and configuration evidence. It writes a current-state document anchored to the git snapshot, with every claim cited and labeled by evidence strength.

Current-state documentation records what is actually implemented and observable in the repository, while target architecture describes intended future design. This Skill only produces current-state documentation and explicitly excludes target design, audit verdicts, and recommendations.

Yes, but with limitations. The Skill documents everything provable from repository evidence and marks runtime-only, organizational, or production facts as UNKNOWN rather than guessing, so readers know exactly what still needs external confirmation.

No. The run is read-only except for writing the single approved architecture document, by default docs/architecture/current-state.md. It never changes product code, tests, or configuration.

Avoid it when you need architecture audit findings, quality scoring, or target design proposals. Those require separate audit or design skills; this Skill deliberately separates observed facts from evaluation and prescription.