doc-coauthoring

Guide structured co-authoring of proposals, specs, and RFCs with reader testing.

Updated May 5, 2026
One-click install
npx skills add https://github.com/XCmiaow/cc-deploy --skill doc-coauthoring-xcmiaow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/XCmiaow/cc-deploy/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/XCmiaow/cc-deploy --skill doc-coauthoring-xcmiaow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams and individuals turn messy ideas into structured, reader-friendly documentation by guiding collaboration through context gathering, iterative refinement, and final reader testing.

Core Features & Use Cases

  • Context Gathering: Prompts users for document type, audience, goals, constraints, and supporting materials so the guide can produce better drafts.
  • Refinement & Structure: Builds the document section-by-section with clarifying questions, options/alternatives, curation, drafting, and iterative edits.
  • Reader Testing: Verifies the document works for others by simulating how a fresh reader would ask questions and identifying blind spots or ambiguities.

Quick Start

Tell the skill: “I need to write a PRD for [product], for [audience], and I want a structured doc with a reader-testing pass—start 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 structured PRD from scattered context and partial ideas?

To write a structured PRD from scattered context, use a guided co-authoring workflow that gathers document type, audience, and goals first, then builds the document section-by-section with iterative curation and drafting.

What is the best way to co-author technical specs and decision docs?

The best way to co-author technical specs is through an iterative process that drafts sections individually, asks clarifying questions, and runs a final reader-testing pass to simulate fresh reader feedback and identify ambiguities.

Can I use this co-authoring workflow to turn messy ideas into reader-friendly documentation?

Yes, you can use this co-authoring workflow to turn messy ideas into reader-friendly documentation by systematically gathering constraints and supporting materials before drafting the structured document.

How does reader testing work for technical writing and RFCs?

Reader testing for technical writing works by simulating how a fresh reader interacts with the RFC, asking questions to uncover blind spots, gaps, and inconsistencies in the drafted document before finalizing it.

Do I need to provide complete notes to start co-writing a proposal?

No, you do not need complete notes to start co-writing a proposal; the workflow is designed to handle partial or scattered context by prompting you for document goals, audience, and constraints during the initial gathering phase.