doc-coauthoring

Guides collaborative document creation through context gathering, iterative drafting, and reader testing.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/quangtuyennguyen/loan-application-workflow --skill doc-coauthoring-quangtuyennguyen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/quangtuyennguyen/loan-application-workflow/tree/main/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/quangtuyennguyen/loan-application-workflow --skill doc-coauthoring-quangtuyennguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical specs alone often leads to blind spots, unclear structure, and content that confuses readers. This Skill provides a structured three-stage workflow that turns document writing into a guided collaboration, ensuring the final doc actually works for its intended audience. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through targeted questions and info dumps before any drafting begins. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates them with the user, then drafts and iteratively refines each section using surgical edits. - Reader Testing: Validates the finished document with a fresh, context-free reviewer (sub-agent or manual test) to catch ambiguity, false assumptions, and contradictions. - Use Case: A product manager needs to write a decision doc for a new architecture. The workflow gathers stakeholder context, drafts each section through brainstorming and curation, then tests the doc with a fresh reader to confirm it stands on its own. ## Quick Start Ask the assistant to guide you through writing a technical spec or decision doc using the structured co-authoring workflow.

Frequently Asked Questions about doc-coauthoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a technical spec or decision doc with AI assistance?▼

Use a structured co-authoring workflow: first dump all relevant context while answering clarifying questions, then build the document section by section through brainstorming and curation, and finally test it with a fresh reader to catch blind spots.

What is the best workflow for drafting a proposal collaboratively?▼

A three-stage approach works well: context gathering to close knowledge gaps, iterative section-by-section refinement with brainstorming of 5-20 options per section, and reader testing to verify the document works for people without prior context.

How can I test whether my document is clear to readers?▼

Use reader testing: predict 5-10 questions real readers would ask, then have a fresh AI instance with no prior context answer them using only the document. Misinterpretations reveal ambiguity, false assumptions, or missing context to fix.

Can this workflow use content from Slack or Google Docs?▼

Yes, if integrations or MCP connectors are available, the workflow can pull context directly from messaging channels and shared documents. Without connectors, you can paste the relevant content manually into the conversation.

When should I skip the structured workflow and write freeform?▼

Freeform writing suits short or low-stakes documents where structured iteration adds overhead. The guided workflow is most valuable for substantial documents like RFCs, PRDs, and decision docs where reader clarity matters.