By name: doc-coauthoring description: Collaborative technical writing workflow for specs, architecture notes, and research manuscripts. Use when drafting or revising structured documents that require clear audience targeting, iterative refinement, and consistency checks. license: MIT metadata: author: local-adapted version: "1.0.0"
Doc Co-Authoring
When to apply
- Writing technical specs, architecture decisions, implementation plans, or paper sections.
- Existing draft needs restructuring, tightening, or consistency cleanup.
Co-authoring stages
- Context capture
- Audience, purpose, constraints, and expected decisions.
- Structure design
- Build section outline and acceptance criteria per section.
- Section drafting
- Draft one section at a time with explicit claims and evidence.
- Refinement
- Remove ambiguity, tighten logic flow, unify terminology.
- Reader check
- Simulate reader questions and patch weak spots.
Quality checks
- Terms are defined once and used consistently.
- Claims are traceable to data/evidence.
- Scope boundaries and non-goals are explicit.
- Action items include owner and completion signal.
Output style
- Keep headings informative.
- Prefer concise paragraphs and scannable bullets.
- End with decisions, risks, and next steps.