skills.rest
GayanKavinda
GayanKavindaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

doc-coauthoring

Guide collaborative drafting of structured documents with reader testing.

Updated Mar 17, 2026
Search Tags:#documentation#editing#proposals#rfc#specs#coauthoring#reader testing
One-click install
npx skills add https://github.com/GayanKavinda/gayankavinda.github.io --skill doc-coauthoring-gayankavinda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/GayanKavinda/gayankavinda.github.io/tree/main/skills/skills/doc-coauthoring
Command: npx skills add https://github.com/GayanKavinda/gayankavinda.github.io --skill doc-coauthoring-gayankavinda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps people turn messy ideas, partial context, and scattered references into clear, structured documentation that actually works for readers.

Core Features & Use Cases

  • Guided Discovery: Gathers the right context up front with targeted questions instead of forcing the user to organize everything first.
  • Iterative Drafting: Builds documents section by section, brainstorming options, curating what matters, and refining each part through feedback.
  • Reader Testing: Checks whether a fresh reader would understand the document, surfacing ambiguities, gaps, and contradictions before publication.
  • Use Case: Drafting a technical spec, RFC, proposal, decision doc, or internal guide that needs to be precise, readable, and defensible.

Quick Start

Use the doc-coauthoring skill to help me draft a technical spec for our new API.

Frequently Asked Questions about doc-coauthoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I co-author technical specs and RFCs collaboratively?▼

You can co-author technical specs and RFCs by using a tool that gathers context up front, drafts sections iteratively, and runs reader testing to resolve ambiguities before publication.

What is the best way to draft a high-stakes proposal that is easy for external readers to understand?▼

The best way to draft a high-stakes proposal is to build it section by section, brainstorming options and refining each part through feedback to ensure clarity and defensibility for external readers.

How do I check if my decision doc is clear enough for a fresh reader?▼

To check if your decision doc is clear for a fresh reader, perform reader testing to surface ambiguities, gaps, and contradictions, ensuring the document works as intended before publication.

Do I need to organize all my context before drafting an internal guide?▼

You do not need to organize all context before drafting an internal guide; the process gathers the right context up front through targeted questions instead of forcing prior organization.

Can I use this approach to turn messy ideas into structured documentation?▼

Yes, you can turn messy ideas, partial context, and scattered references into structured documentation by iteratively drafting and curating what matters to reduce ambiguity.

Related Skills

Explore More Content & Communication Skills→
jaydubya818jaydubya818

product-marketing-context

Create and update product marketing context documents from codebase analysis.

Community
Intermediate
chadanandachadananda

doc-coauthoring

Guide teams through a three-stage co-authoring workflow for reader-ready documents.

Community
Basic
GeargrindadminGeargrindadmin

doc-coauthoring

Guide structured co-authoring of technical specifications with iterative drafting and reader testing.

Community
Advanced
iredrion-imgiredrion-img

doc-coauthoring

Guides teams through co-authoring structured documents with Context Gathering, Refinement & Structure, and Reader Testing workflows.

Community
Advanced