187DOCS skill
187DOCS — Documentation architecture engine.
Designs, writes, audits, and repairs documentation systems following the Diátaxis framework: READMEs, install guides, how-to guides, reference docs, API docs, SOPs, changelogs, and drift repair.
Triggers
How to invoke 187DOCS
| Trigger | |
|---|---|
| /187docs | |
| 187DOCS | |
| docs this | |
| write README | |
| install guide | |
| quickstart | |
| how to guide | |
| API docs |
Use cases
When to route to 187DOCS
Project docs and READMEs
Install guides, quickstarts, and how-to guides
API docs, SOPs, and user manuals
Docs drift audits and cross-surface sync
Output contract
What 187DOCS delivers
- 1Audience & doc-type mapping
- 2Structure & draft content
- 3Code / command examples
- 4Cross-references
- 5Drift repair notes
- 6187WRITE polish pass
Routing
When to hand off to another skill
| Route to | When |
|---|---|
| 187write | polishing public-facing copy |
| 187research | docs cite papers, APIs, or datasets |
| 187ACCESS+ / 187INCLUDE+ | publishing public docs |
| 187publish | final sync across surfaces |
Templates
Artifacts 187DOCS produces
| Template | When to use |
|---|---|
| README.md | Project landing doc |
| install-guide.md | Step-by-step environment setup |
| quickstart.md | First success in minutes |
| how-to-guide.md | Goal-oriented task instructions |
| reference-doc.md | Fact lookup, commands, schemas |
| explanation-doc.md | Conceptual background and why |
| troubleshooting-guide.md | Error diagnosis and recovery |
| SOP.md | Repeatable operational procedure |
| API-docs.md | API endpoint and schema reference |
| changelog-entry.md | Version change entry |