doc-coauthoring

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

Updated Oct 7, 2022
One-click install
npx skills add https://github.com/tamagusko/linux-cfg --skill doc-coauthoring-tamagusko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/tamagusko/linux-cfg/tree/main/dotfiles/claude/skills/doc-coauthoring
Command: npx skills add https://github.com/tamagusko/linux-cfg --skill doc-coauthoring-tamagusko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing substantial documents like specs, RFCs, and decision docs alone often produces drafts full of blind spots, missing context, and assumptions that confuse readers. This Skill structures the co-authoring process so the final document actually works for its intended audience. ## Core Features & Use Cases - Three-Stage Workflow: Walks through Context Gathering, Refinement & Structure, and Reader Testing with clarifying questions at each step. - Section-by-Section Drafting: Brainstorms 5-20 options per section, curates them with the user, then drafts and iteratively refines using surgical edits. - Fresh-Reader Testing: Validates the finished document with a context-free reader (sub-agent or manual test) to catch ambiguity and hidden assumptions. - Use Case: A engineer needs to write a decision doc for a migration plan. The Skill gathers organizational context, scaffolds sections from the decision-doc template, drafts each part iteratively, then tests whether a fresh reader can explain the decision back accurately. ## Quick Start Ask the assistant to help you co-author a decision doc using the structured doc-coauthoring workflow, starting 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 co-author a technical spec or decision doc with Claude?

Start the doc-coauthoring workflow, which guides you through three stages: context gathering with clarifying questions, section-by-section drafting with brainstorming and curation, and reader testing. You can answer in shorthand and dump context in any format.

What document types does this workflow support?

It includes default section scaffolds for decision docs, technical specs, proposals, and RFCs in its references. For other document types, it suggests 3-5 appropriate sections based on the doc type and any template you provide.

Does the reader testing stage work without Claude Code sub-agents?

Yes. Without sub-agents, the workflow gives you manual testing instructions: open a fresh Claude conversation, paste the document, and ask the predicted reader questions plus ambiguity and contradiction checks.

Can it pull context from Slack or Google Drive automatically?

Only if connectors or MCP integrations are actually available in your environment, and only after your consent. Without connectors, it asks you to paste or summarize the relevant content directly.

When should I skip this structured workflow?

Skip it for short or low-stakes writing where a three-stage process adds overhead. The workflow is designed for substantial documents like specs and RFCs where reader comprehension and blind-spot detection matter.