doc-coauthoring

Guide staged co-authoring of structured documents with context gathering and reader testing.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/yashs33244/my-mac-claude --skill doc-coauthoring-yashs33244
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/anthropic/doc-coauthoring
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill doc-coauthoring-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of producing documentation that’s hard to write efficiently and even harder for others to understand, by guiding co-authoring from missing-context discovery through iterative drafting to reader-ready validation.

Core Features & Use Cases

  • Context Gathering: Ask targeted questions to collect meta-context (doc type, audience, impact, constraints) and prompt an efficient context dump so the resulting draft matches what readers need.
  • Refinement & Structure: Build the document section-by-section with structured brainstorming, user-driven keep/remove/combine curation, and iterative surgical edits instead of uncontrolled rewriting.
  • Reader Testing: Validate the doc by testing it against realistic reader questions (or giving the user steps to do it manually) to detect ambiguity, false assumptions, and missing explanations before others read it.
  • Use Cases: Technical specs, PRDs, RFCs, decision docs, proposals, and any structured writing where context transfer and reader comprehension are critical.

Quick Start

Use the doc-coauthoring skill to build your PRD or spec in stages: first gather the right context, then draft each section with curation, and finally test the result with fresh-reader questions.

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 PRD that is ready for reader testing?

A structured co-authoring workflow guides technical spec and PRD creation by collecting context, refining sections iteratively, and testing drafts against realistic reader questions to catch ambiguities before publication.

What is the best way to co-author an RFC or decision doc iteratively?

Co-authoring an RFC or decision doc iteratively requires staged context collection and section-by-section refinement with explicit curation, ensuring surgical edits rather than uncontrolled rewrites.

How do I gather context before drafting a proposal or technical documentation?

Gather context for proposals by answering targeted questions about doc type, audience, impact, and constraints, followed by an efficient context dump to ensure the draft matches reader requirements.

Does this structured co-authoring workflow support testing documentation against reader questions?

Yes, the structured co-authoring workflow includes reader testing by validating documents against realistic reader questions to detect false assumptions, ambiguities, and missing explanations before publication.

Can I use this workflow for any structured documents evolving through review and iteration?

Yes, this workflow applies to any structured documents evolving through review, including technical specs, PRDs, RFCs, decision docs, and proposals where context transfer and reader comprehension are critical.

Why does my documentation draft fail to convey the right context to readers?

Documentation drafts fail to convey context when missing-context discovery is skipped; applying targeted context gathering before drafting ensures the result is context-complete and reader-ready.