doc-coauthoring

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

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill doc-coauthoring-ttnhan18062000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/ttnhan18062000/rpg-based-simulation/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill doc-coauthoring-ttnhan18062000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical specs alone often produces documents that make sense to the author but confuse readers. This Skill provides a structured three-stage workflow that closes context gaps, builds documents section by section, and validates them with fresh-reader testing before publication. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through structured questions and info dumps, with optional integration to shared documents and team channels. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates content with the user, drafts into artifacts or files, and iterates through surgical edits. - Reader Testing: Tests the finished document with a fresh AI instance (sub-agent or manual) to catch ambiguities, false assumptions, and contradictions before real readers see it. - Use Case: A product manager drafting a decision doc uses the workflow to dump context, iteratively build the proposal section, then verify a fresh reader can correctly answer likely questions about the decision. ## Quick Start Ask the assistant to guide you through co-authoring a decision doc or technical spec using the structured three-stage 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 and answer clarifying questions, then build the spec section by section through brainstorming and curation, and finally test the draft with a fresh reader to catch blind spots before sharing it.

How do I draft a decision doc or RFC collaboratively?

Start with context gathering covering audience, constraints, and alternatives considered. Then draft the core proposal section first since it has the most unknowns, refine through iterative edits, and leave summary sections for last.

Can this workflow use content from Slack or Google Docs?

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

What is reader testing for documents?

Reader testing validates a draft by having a fresh AI instance with no prior context answer likely reader questions. It surfaces ambiguities, assumed knowledge, and contradictions that authors miss because they already understand the material.

When should I skip the structured workflow and write freeform?

Freeform writing suits short or low-stakes documents where reader ambiguity carries little risk. The structured workflow pays off for decision docs, specs, and proposals that many stakeholders will read and act on.