Organise project documentation with AI
Identify the current source for each subject and version, distinguish drafts from supported older material and test the structure against real reader tasks.
Organise project documentation with AI by asking why two apparently similar pages exist. An order-export specification explains what users receive, while a design note explains how the system produces it. The docs-structure skill helps clarify those responsibilities before suggesting a move or merger.
A supported older version may still need its own current instructions. Archive a document because it has been superseded, not merely because its date is old. A small project may need a single clear link rather than a hierarchy of indexes.
What it does
- Assign a clear responsibility to each document or directory.
- Identify one current body of guidance for a topic and version.
- Mark drafts and link superseded material to its replacement.
- Test navigation from an entry point using a realistic task.
- Plan changes before moving files or updating references.
Install and use
- Use the official docs-governance plugin with its shared resources and an authorised repository. Git supports history checks, and optional local helpers use Python 3.
- Ask, “Plan a layout for our export documentation. A developer should be able to find both behaviour and design without guessing which version applies.”
- Test the proposed routes and authorise any actual reorganisation before files are moved.
FAQ
Source
Made by qshanx. Original skill: docs-structure, published on GitHub under the MIT licence.
View on GitHub