mcpbeat

Doc Coauthoring

dokhacgiakhoa/doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
context cost
the whole folder, loaded on every use
20
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill doc-coauthoring

What comes with it

13 684 bytes besides the instruction
sub-skills/exit-condition-both-approaches.md
sub-skills/info-dumping.md
sub-skills/initial-questions.md
sub-skills/near-completion.md
sub-skills/quality-checking.md
sub-skills/step-1-clarifying-questions.md
sub-skills/step-1-predict-reader-questions.md
sub-skills/step-2-brainstorming.md
sub-skills/step-2-setup-testing.md
sub-skills/step-2-test-with-sub-agent.md
sub-skills/step-3-additional-checks.md
sub-skills/step-3-curation.md
sub-skills/step-3-run-additional-checks.md
sub-skills/step-4-gap-check.md
sub-skills/step-4-iterate-based-on-results.md
sub-skills/step-4-report-and-fix.md
sub-skills/step-5-drafting.md
sub-skills/step-6-iterative-refinement.md
sub-skills/testing-approach.md

The instruction itself

24 sections, as written by the author

Doc Co-Authoring Workflow

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

When to Offer This Workflow

Trigger conditions:

  • User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up"
  • User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC"
  • User seems to be starting a substantial writing task

Initial offer:

Offer the user a structured workflow for co-authoring the document. Explain the three stages:

  • Context Gathering: User provides all relevant context while Claude asks clarifying questions
  • Refinement & Structure: Iteratively build each section through brainstorming and editing
  • Reader Testing: Test the doc with a fresh Claude (no context) to catch blind spots before others read it

Explain that this approach helps ensure the doc works well when others read it (including when they paste it into Claude). Ask if they want to try this workflow or prefer to work freeform.

If user declines, work freeform. If user accepts, proceed to Stage 1.

Stage 1: Context Gathering

Goal: Close the gap between what the user knows and what Claude knows, enabling smart guidance later.

🧠 Knowledge Modules (Fractal Skills)

1. Initial Questions

2. Info Dumping

3. Step 1: Clarifying Questions

4. Step 2: Brainstorming

5. Step 3: Curation

6. Step 4: Gap Check

7. Step 5: Drafting

8. Step 6: Iterative Refinement

9. Quality Checking

10. Near Completion

11. Testing Approach

12. Step 1: Predict Reader Questions

13. Step 2: Test with Sub-Agent

14. Step 3: Run Additional Checks

15. Step 4: Report and Fix

16. Step 1: Predict Reader Questions

17. Step 2: Setup Testing

18. Step 3: Additional Checks

19. Step 4: Iterate Based on Results

20. Exit Condition (Both Approaches)

How to use it

Copy the folder

Take dokhacgiakhoa/doc-coauthoring from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.