doc-coauthoring

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

9|2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/AbdullahMalik17/Hacathan_5 --skill doc-coauthoring-abdullahmalik17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/AbdullahMalik17/Hacathan_5/tree/main/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/AbdullahMalik17/Hacathan_5 --skill doc-coauthoring-abdullahmalik17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and specs alone often produces documents that make sense to the author but confuse readers. This Skill structures the co-authoring process so context is fully transferred, each section is deliberately refined, and blind spots are caught before others read the doc. ## Core Features & Use Cases - Three-Stage Workflow: Context Gathering, Refinement & Structure, and Reader Testing guide the document from raw ideas to a reader-ready draft. - Section-by-Section Iteration: Brainstorming, curation, drafting, and surgical edits for each section of PRDs, design docs, decision docs, RFCs, and technical specs. - Reader Testing: Predicts reader questions and validates the document with a fresh, context-free reviewer to expose ambiguity and assumed knowledge. - Use Case: A product manager needs to write a decision doc for a migration plan. The Skill gathers organizational context, drafts each section through structured feedback, then tests the final doc against realistic reader questions before it is shared with the team. ## Quick Start Ask the assistant to help you write a design doc or proposal using the structured co-authoring workflow, starting with context gathering.

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 design doc with AI assistance?▼

Start the co-authoring workflow by sharing the document type, audience, and desired impact. The process gathers your context, drafts each section through brainstorming and curation, then tests the finished doc against realistic reader questions.

What document types does this writing workflow support?▼

The workflow supports structured documents including PRDs, technical specs, design docs, decision docs, RFCs, and proposals. It adapts section suggestions based on the document type and any template you provide.

How does reader testing catch documentation blind spots?▼

Reader testing generates 5-10 questions a real reader would ask, then evaluates the document with a fresh reviewer that has no prior context. Wrong answers, ambiguity, and assumed knowledge are reported so gaps can be fixed before sharing.

Can I use this workflow without integrations or artifacts?▼

Yes. Without integrations, you paste context directly instead of pulling from Slack or Google Drive. Without artifacts, the draft is created as a markdown file in the working directory, and reader testing is done manually in a fresh 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 workflow is most valuable for substantial documents that multiple stakeholders will read and act on.