doc-coauthoring

Guide structured document co-authoring from context gathering to reader testing.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/Posteriot/makalah-app --skill doc-coauthoring-posteriot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Posteriot/makalah-app/tree/main/docs/skill-per-stage/example/anthropic/doc-coauthoring
Command: npx skills add https://github.com/Posteriot/makalah-app --skill doc-coauthoring-posteriot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents documentation chaos by guiding Claude through a phased workflow that captures missing context, shapes structure, and validates readability before publishing.

Core Features & Use Cases

  • Stage 1 – Context Gathering: Ask meta-questions about doc type, audience, impact, templates, constraints, and encourage info dumps so Claude truly understands the background, integrations, shared documents, and unknowns before drafting anything.
  • Stage 2 – Refinement & Structure: Brainstorm sections, create a scaffold artifact, iterate through clarifying questions, curated content, gap checks, surgical edits, and artifact updates until each section feels solid.
  • Stage 3 – Reader Testing: Predict reader questions, run them (with or without sub-agents), summarize where fresh Claude readers might stumble, and loop back to fix problematic sections before signing off.
  • Use Case: Draft decision docs, technical specs, proposals, or RFCs with a steady process that balances collaboration, iteration, and validation.

Quick Start

Describe your document, audience, and goals, then ask Claude to guide you through the doc-coauthoring workflow so it can gather context, refine structure, and test the reader experience.

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 to prevent documentation chaos?

Structured document co-authoring works by progressing through three stages: gathering context via meta-questions, refining structure through iterative brainstorming and artifact creation, and testing readability by predicting and resolving reader questions.

What is the best way to draft decision documents or RFCs with iterative refinement?

The best way to draft decision documents with iterative refinement is using a workflow that brainstorms sections, creates a scaffold artifact, runs gap checks, and applies surgical edits until each section feels solid.

Can I test the readability of a technical document before publishing it?

Yes, you can test readability before publishing by predicting reader questions, running them to identify where fresh readers might stumble, and looping back to fix problematic sections before signing off.

Does collaborative document drafting work for complex technical workflows requiring context gathering?

Yes, collaborative document drafting handles complex workflows by asking meta-questions about audience, impact, templates, and constraints, while encouraging info dumps to fully understand background and unknowns before drafting.

What are the limitations of using a phased workflow for document collaboration?

A limitation of phased document collaboration is that it requires progressive questioning, brainstorming, artifact creation, and reader testing steps, making it a rigorous process that may be excessive for simple, unstructured content.