doc-coauthoring

Guide multi-stage document co-authoring with context gathering, iterative drafting, and reader testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow to guide users through collaborative document creation. It acts as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.

Core Features & Use Cases

  • Three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing.
  • Triggers for identifying when to offer the workflow (writing docs, proposals, specs, decision docs, RFCs).
  • Interactive Stage 1: Context Gathering with initial questions to elicit meta-context.
  • Stage 2: Refinement & Structure with iterative drafting, brainstorming, and surgical edits.
  • Stage 3: Reader Testing with a "fresh Claude" check for reader-facing clarity.
  • Optional integration with artifacts creation to scaffold documents; supports freeform drafting if user declines structured approach.
  • Suitable for technical specs, proposals, design docs, PRDs, RFCs, decision docs, and other structured documentation tasks.

Quick Start

Start by offering the structured doc co-authoring workflow whenever the user is preparing to write a document such as a technical spec, proposal, or design doc. If the user accepts, proceed to Stage 1 and collect context before drafting.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
What is the best way to structure a technical spec or proposal co-authoring workflow?

A structured co-authoring workflow guides you through context gathering, iterative refinement, and reader testing to ensure technical specs and proposals are clear and validated by readers.

How do I start writing a design doc or RFC using a structured workflow?

Start writing a design doc or RFC by gathering meta-context through initial questions, then refine the structure through iterative drafting and brainstorming before finalizing.

Can I use this guided workflow for decision records and PRDs?

Yes, you can use this guided workflow for decision records, PRDs, and similar structured documentation, applying context gathering, surgical edits, and reader validation stages.

How does reader testing work for technical documentation?

Reader testing for technical documentation uses a fresh perspective check to evaluate reader-facing clarity, asking explicit questions to ensure the document communicates its intent effectively.

Do I need to follow all three stages to draft my document?

No, you do not need to follow all three stages; the workflow supports freeform drafting if you decline the structured approach, though the stages enforce thorough context gathering and validation.