Guide users through structured collaborative documentation creation. Use when user wants to write documentation, update README, create architecture docs, draft proposals, technical specs, decision docs, refactor documentation, create API docs, or document code.
Collaborative workflow for creating documentation that works for readers.
Trigger conditions:
| Variant | Stages | Use For | |---------|--------|---------| | Full Collaborative | Context Gathering → Refinement → Reader Testing | Proposals, specs, decisions, RFCs | | Streamlined Collaborative | Context Gathering → Refinement | READMEs, API docs, architecture guides |
Both variants use collaborative principles (clarifying questions, iterative refinement). Streamlined skips Reader Testing since code docs have different validation (working examples, API accuracy).
Close the gap between what the user knows and what Claude knows. Ask about doc type, audience, desired impact, and template. Encourage info dumping. Ask clarifying questions until understanding is sufficient.
Build the document section by section. For each section: ask clarifying questions, brainstorm options, let user curate, draft, and refine through surgical edits. Use code documentation patterns as scaffolds for READMEs, APIs, etc.
Test the document with a fresh Claude (no context bleed) to verify it works for readers. If sub-agents available, test directly. Otherwise, guide user through manual testing.
When triggered, offer the workflow:
I can help you write that [doc type]. I use a structured workflow that helps
ensure the doc works well when others read it:
1. **Context Gathering**: You share relevant context while I ask clarifying questions
2. **Refinement & Structure**: We build each section through brainstorming and iteration
3. **Reader Testing**: We test the doc with a fresh Claude to catch blind spots
(or skip for code docs like READMEs)
Would you like to try this workflow, or prefer to work freeform?
For code docs, select the appropriate pattern as the starting scaffold:
| Doc Type | Pattern | |----------|---------| | README | Features, Installation, Quick Start, Config, API, Contributing | | API Docs | OpenAPI spec with paths, schemas, examples | | Architecture | Overview, Component Diagram, Components table, Data Flow | | Configuration | Required/Optional vars table, example config | | Module | Purpose, Architecture diagram, Components, Methods table |
See WORKFLOW.md for complete patterns.
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
Manage Trello boards, lists, and cards via the Trello REST API.
Category:productivity