doc-coauthoring

Guides collaborative document creation through context gathering, iterative drafting, and reader testing.

3|1|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/PALabs-v1/AI_friend --skill doc-coauthoring-palabs-v1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/PALabs-v1/AI_friend/tree/main/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/PALabs-v1/AI_friend --skill doc-coauthoring-palabs-v1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and specs alone often produces documents that make sense to the author but confuse readers. This Skill structures the co-authoring process so context is fully transferred, each section is deliberately refined, and blind spots are caught before others read the doc. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through structured questions and info dumps, optionally pulling from connected tools like Slack or Google Drive. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates them with the user, drafts content, and iterates with surgical edits. - Reader Testing: Tests the finished document with a fresh, context-free reader (via sub-agents or a manual fresh conversation) to surface ambiguity, false assumptions, and contradictions. - Use Case: A product manager drafting a decision doc uses the workflow to dump team context, build the proposal section through curated brainstorming, and verify a fresh reader can correctly answer likely questions before sharing it with stakeholders. ## Quick Start Ask the assistant to guide you through the doc co-authoring workflow to draft a decision doc for your upcoming project proposal.

Frequently Asked Questions about doc-coauthoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a decision doc with an AI assistant?

Use a structured co-authoring workflow: first dump all project context and answer clarifying questions, then build each section through brainstorming and curated drafting, and finally test the finished doc with a fresh reader to catch blind spots before sharing it.

How to test whether a document is clear to readers?

Reader testing validates clarity by having a fresh AI instance with no prior context answer realistic reader questions about the document. Wrong answers, ambiguity flags, or assumed-knowledge gaps reveal sections that need revision.

Can this workflow pull context from Slack or Google Drive?

Yes, if integrations or MCP servers are available, the workflow can read team channels, threads, and shared documents directly during context gathering. Without integrations, you paste the relevant content manually or enable connectors in settings.

What types of documents does this workflow support?

It supports structured documents such as technical specs, decision docs, RFCs, PRDs, and proposals. The workflow adapts section suggestions to the document type and any template you provide.

When should I skip the structured workflow and write freeform?

Freeform writing fits short or low-stakes documents where reader ambiguity carries little risk. The structured workflow is most valuable for substantial documents that multiple stakeholders will read and act on.