Documenting Legacy Codebases

by riekelt85e53729dd95No license28 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 weeks ago

Use when documenting an existing codebase whose documentation is missing, stale, or untrusted - an inherited system, a legacy application, a repo where the docs lie - or when regrounding a documentation tree against the code, or when someone asks what a system actually does. Encodes the survey-first inventory, the writer-side evidence hierarchy, depth-per-surface rules, the refactor test, dead-or-alive proofs, the quirks-and-findings split, the coverage ledger, the parallel campaign, and the docs-tree skeleton. Use whenever documentation must be reconstructed from the code rather than written alongside a change.

Only the file list is public. File contents are available once the skill is installed in a workspace.

PathSizeType
SKILL.md14.8 KBtext/markdown

Source and attribution

Source:riekelt/technical-writerinplugins/technical-writer/skills/documenting-legacy-codebasesat commit85e5372

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal