doc-coauthoring · Doc Co-Authoring Workflow
Guide structured collaborative document writing: PRDs, design docs, decision docs, technical specs.
A three-stage process: context gathering (you dump context, it asks clarifying questions) → section-by-section refinement (clarify, brainstorm 5-20 points per section, you curate, it drafts and iterates) → reader testing (a context-free fresh Claude reads the doc and answers preset questions, exposing blind spots). You can switch to freeform writing at any time.
Example invocation: "Help me write a technical spec."
Full brief
Positioning
doc-coauthoring is a structured document-writing workflow: when the user wants a document, proposal, technical spec, or decision doc, it guides a three-stage process instead of drafting immediately.
Core capabilities
- Stage 1 — context gathering: asks doc type, audience, desired impact, templates and constraints; encourages context dumps (background, discussions, rejected alternatives, org context, timelines); follows with 5-10 clarifying questions.
- Stage 2 — section refinement: per section: clarify → brainstorm 5-20 points → user curates keep/remove/combine → draft → iterative surgical edits; asks what can be cut after 3 unchanged iterations; full re-read at 80%+ for flow and redundancy.
- Stage 3 — reader testing: predicts reader questions, tests with a context-free fresh Claude (sub-agent) answering them, checks ambiguity/assumptions/contradictions; loops back to refine on blind spots.
- Final review: recommends the user's own read-through and fact/link verification; closing tips (appendices, linking the conversation).
- Flexibility: stages can be skipped or switched to freeform anytime; acknowledges cost when the user is frustrated and offers ways to move faster.
Workflow
- Doc request → explain the three-stage process; confirm workflow vs. freeform
- Context gathering: meta-questions → user dump → clarifying questions → confirm readiness
- Section refinement: agree structure (start with the section of highest uncertainty) → placeholder scaffold → per-section clarify/brainstorm/curate/draft/iterate
- Near-complete full re-read for flow and redundancy
- Reader testing: predict questions → fresh Claude answers → fix blind spots → re-refine
- Final review and closing tips
Inputs & outputs
| Input | Required | Notes |
|---|---|---|
| Document need | Yes | Doc type and topic |
| Background | Recommended | Context the user dumps |
Output: the collaboratively completed document (artifact or markdown file).
Fit
- PRDs, technical specs, design docs
- Decision docs, RFCs
- Substantive writing that must hold up for other readers
Before you start
- No API key.
- The process itself costs time: right for important documents; allow stage-skipping or freeform when the user is in a hurry.
- Learn the user's style: ask them to point at what to change rather than rewriting the whole doc.
doc-coauthoring is part of the Aiglade Skill library. Invoke it from the Aiglade chat box in plain language.