RepoAI
Browse MCPs

Doc Coauthoring

88TrustedInstructions only

Systematic process for crafting technical specs, proposals, and project documentation.

What it does

Doc Coauthoring transforms the assistant into a structured project partner for long-form writing tasks. Instead of drafting in isolation, the assistant initiates a three-stage engagement model to bridge the knowledge gap between your intent and the final output.

By moving through phases of context acquisition, iterative drafting, and simulated reader evaluation, the assistant ensures the final document is technically sound and logically arranged. This approach is designed to catch blind spots early and verify that the content remains coherent for anyone else who might analyze or reference it later.

When it earns its place

Reach for it when…

Apply this when initiating a complex writing project such as a technical design document, a formal business proposal, a product requirements document, or a significant decision record. It is particularly effective when you have scattered information across multiple sources that needs to be consolidated into a professional, cohesive format.

Look elsewhere when…

Do not use this for quick communications, emails, or short status updates where the overhead of a formal coauthoring cycle is unnecessary. This is also not intended for creative writing, fictional narratives, or content that requires a non-standard, highly subjective stylistic approach rather than a structured information design.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • Help me draft a technical spec for this new feature
  • I need to write a proposal for the project stakeholders
  • Can we work together on this design document
  • I am starting a new PRD and need some help structuring it

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch main https://github.com/anthropics/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/doc-coauthoring ~/.claude/skills/doc-coauthoring

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/skills/skills/doc-coauthoring .claude/skills/doc-coauthoring

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server

Doc Coauthoring changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →