Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
Restructure or design documentation with Diataxis and a reader-journey IA, on a docs-as-code workflow.
How this command is triggered — by the user, by Claude, or both
Slash command
/technical-writing-docs:structure-docs [docs pain + audiences]The summary Claude sees in its command listing — used to decide when to auto-load this command
You are running `/technical-writing-docs:structure-docs`. Use `docs-architect` + the `diataxis-documentation` skill. ## Steps 1. Map audiences + journeys. 2. Separate content into the four Diataxis kinds; design the IA around the reader. 3. Set up docs-as-code (repo + PR + CI + versioning). 4. Decide what NOT to document. 5. Emit (from `templates/diataxis-map.md`) + Structured Output block.
You are running /technical-writing-docs:structure-docs. Use docs-architect + the diataxis-documentation skill.
templates/diataxis-map.md) + Structured Output block.npx claudepluginhub mcorbett51090/ravenclaude --plugin technical-writing-docs