doc-coauthoring

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

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/sshekhar-04/SIH_PS_26151 --skill doc-coauthoring-sshekhar-04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/sshekhar-04/SIH_PS_26151/tree/main/.agents/Skills/doc-coauthoring
Command: npx skills add https://github.com/sshekhar-04/SIH_PS_26151 --skill doc-coauthoring-sshekhar-04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical specs alone often leads to blind spots, unclear structure, and documents that confuse readers. This Skill provides a structured three-stage workflow that turns document creation 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 structured questions and info dumps before any drafting begins. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates content with the user, drafts, and iterates with surgical edits until each section is polished. - Reader Testing: Validates the finished document with a fresh AI reader (sub-agent or manual testing) to catch ambiguities, false assumptions, and contradictions before publication. - Use Case: A product manager needs to write a decision doc for a new architecture. The Skill gathers context about stakeholders and constraints, drafts each section iteratively, then tests whether a fresh reader can correctly answer questions using only the document. ## 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 with AI assistance?

Use a structured co-authoring workflow: first dump all project context, then build the spec section by section through brainstorming and curation, and finally test the draft with a fresh reader. This catches gaps that solo drafting typically misses.

How to structure a decision doc or design doc?

Start with the section containing the most unknowns, usually the core proposal or technical approach, and leave summary sections for last. If unsure of the structure, the workflow suggests 3-5 sections appropriate for your document type.

Can this workflow use my existing documents and templates?

Yes. You can share a template file or link, and the workflow will follow its format. If integrations like Slack, Google Drive, or SharePoint are connected, it can pull context directly from team channels and shared documents.

What is reader testing for documents?

Reader testing validates a document by having a fresh AI instance with no prior context answer realistic reader questions using only the doc. It surfaces ambiguities, assumed knowledge, and contradictions before real readers encounter them.

When should I skip the structured workflow and write freeform?

Freeform writing suits short or informal documents where structured iteration adds overhead. The workflow is most valuable for substantial documents like specs, proposals, and decision docs that multiple stakeholders will read.