doc-coauthoring

Guides staged co-authoring of technical documents from context gathering to reader testing.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/notaustindaniels/second-brain-skills --skill doc-coauthoring-notaustindaniels
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/notaustindaniels/second-brain-skills/tree/main/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/notaustindaniels/second-brain-skills --skill doc-coauthoring-notaustindaniels

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through a structured co-authoring workflow for documentation. It helps teams efficiently transfer context, refine content through iteration, and verify the doc works for readers.

Core Features & Use Cases

  • Stage-guided workflow: Context Gathering, Refinement & Structure, Reader Testing to orchestrate doc creation from initial idea to reader-ready draft.
  • Trigger-based activation: Suggests the workflow when users mention writing docs, proposals, specs, design docs, RFCs, or similar tasks.
  • Interactive coaching: Acts as an active guide, asking clarifying questions and iteratively drafting sections.
  • Reader testing: Includes reader testing to catch gaps and blind spots before sharing.
  • Flexible to multiple document types: Technical specs, PRDs, decision docs, proposals, runbooks, SOPs.

Quick Start

Start by stating you want to co-author a document and indicate the doc type and audience. The assistant will begin Stage 1 (Context Gathering) and ask clarifying questions. It will then proceed through Stage 2 (Refinement & Structure) and Stage 3 (Reader Testing) with iterative drafting and feedback.

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 proposals with a structured workflow?

Co-authoring technical specs and proposals requires a stage-guided workflow that moves through context gathering, refinement, and reader testing to produce reader-ready documents. This approach iteratively drafts sections while catching gaps before sharing.

What is the best way to structure a documentation workflow for decision docs?

A structured documentation workflow for decision docs uses interactive coaching to gather context, refine structure, and test with readers. This ensures the final document catches blind spots and is ready for the target audience.

Can I use this co-authoring workflow for runbooks and SOPs?

Yes, the co-authoring workflow applies flexibly to runbooks, SOPs, PRDs, and RFCs. It guides you through context gathering and iterative drafting regardless of the specific structured document type.

Do I need any external setup to start co-authoring documents?

No external setup is required to start co-authoring documents. You simply state your document type and audience, and the workflow begins by asking clarifying questions to gather context.

How does reader testing work for documentation drafts?

Reader testing for documentation drafts works by evaluating the iteratively refined content to catch gaps and blind spots. This stage ensures the document works effectively for readers before it is shared.

When should I use a stage-guided workflow for writing RFCs?

Use a stage-guided workflow for writing RFCs when you need to efficiently transfer context, refine content through iteration, and verify the document works for readers before final distribution.