Docs Restructuring

Restructure developer documentation whose structure has failed — the heading tree no longer predicts content, one list mixes concepts with invariants and procedures, half a document sits under an unrelated parent, or the same fact is maintained in several places. Rebuild the document around the four reader questions (understand / not break / do / look up), give every fact exactly one canonical home with pointers elsewhere, and verify with a move map that no passage is lost and no inbound link breaks. Structure only — per-unit tightening of comments and sentences is the comment-pruning skill's job; run it after this one. Use when a README or docs set has grown past navigability, when readers can't find things they know are written down, or when asked to reorganize, restructure, or split documentation.

knokmki612 Updated

File contents

knokmki612/skills commit 4c24ef09f0

Frequently asked questions

npx get-skill add knokmki612/docs-restructuring