doc-coauthoring

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

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ramshan00/hackaton --skill doc-coauthoring-ramshan00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/ramshan00/hackaton/tree/main/Hackathon2-phase2/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/ramshan00/hackaton --skill doc-coauthoring-ramshan00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical specs alone often produces documents full of blind spots, missing context, and unclear sections that confuse readers. This Skill provides a structured three-stage workflow that transfers your context to the AI, builds the document section by section, and validates it with fresh-reader testing before anyone else sees it. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through targeted questions and info dumps, optionally pulling from connected tools like Slack or Google Drive. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates them with your feedback, drafts content, and iterates through surgical edits. - Reader Testing: Tests the finished document with a fresh AI instance (no prior context) to catch ambiguities, false assumptions, and contradictions before real readers do. - Use Case: You need to write a decision doc for a migration proposal. The workflow gathers your technical and political context, drafts each section iteratively, then verifies a fresh reader can correctly answer likely questions about the doc. ## Quick Start Ask the AI to guide you through the doc co-authoring workflow to draft a technical design document for your upcoming project.

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

Use a structured co-authoring workflow: first dump all project context while the AI asks clarifying questions, then build each section through brainstorming and iterative edits, and finally test the draft with a fresh AI session to catch blind spots before sharing it.

How to test if my documentation is clear to readers?

Test the document with a fresh AI conversation that has no prior context. Paste the doc, ask questions a real reader would ask, and check whether the answers are correct. Also ask what the doc assumes readers already know and whether anything is ambiguous or contradictory.

What types of documents does this workflow support?

The workflow supports structured documents such as technical specs, decision docs, PRDs, RFCs, and proposals. It adapts section suggestions based on the document type and any template you provide during the context gathering stage.

Can I use this workflow with Google Docs or Slack context?

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

When should I skip the structured workflow and write freeform?

Skip the workflow for short, low-stakes documents where reader testing adds little value, or when you already have a clear draft and only need light editing. The workflow is designed for substantial documents where clarity and completeness matter.