doc-coauthoring

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

Updated May 23, 2026
One-click install
npx skills add https://github.com/kiranimmadi2/promptforge-ai --skill doc-coauthoring-kiranimmadi2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/kiranimmadi2/promptforge-ai/tree/main/anthropic-skills/skills/doc-coauthoring
Command: npx skills add https://github.com/kiranimmadi2/promptforge-ai --skill doc-coauthoring-kiranimmadi2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and specs alone often produces documents full of blind spots, missing context, and unclear sections that confuse readers. This Skill structures the co-authoring process so the final document actually works for its intended audience. ## Core Features & Use Cases - Three-Stage Workflow: Guides users through Context Gathering, Refinement & Structure, and Reader Testing to build documents section by section. - Iterative Section Drafting: Brainstorms 5-20 options per section, curates with the user, then drafts and refines through surgical edits using artifacts or files. - 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 Skill gathers project context, drafts each section iteratively, then tests whether a fresh reader can correctly answer likely questions before the doc 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?

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

How to test if my documentation is clear to readers?

Reader testing validates clarity by having a fresh reviewer with no prior context answer realistic questions about the document. If the reviewer misinterprets sections or finds ambiguity, those gaps are fixed before sharing the doc with real readers.

What types of documents does this workflow support?

The workflow supports structured documents such as technical specs, decision docs, proposals, PRDs, RFCs, and design docs. It adapts section structure based on the document type and any template the user provides.

Can I use this workflow without integrations like Slack or Google Drive?

Yes, integrations are optional. Without connectors, you paste relevant context, templates, and document content directly into the conversation, and the workflow proceeds identically through its three stages.

What happens if I want to skip a stage in the workflow?

The workflow is flexible and gives you agency to adjust the process. You can decline the structured approach entirely and work freeform, or skip individual stages when they do not fit your needs.