doc-coauthoring

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

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill doc-coauthoring-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/scoots31/engineering-playbook/tree/main/references/doc-coauthoring
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill doc-coauthoring-scoots31

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 document. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through structured questions and info dumps, with optional integration support for pulling content from connected tools. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates them with the user, drafts content, and iterates through surgical edits until each section is complete. - Reader Testing: Tests the finished document with a fresh AI instance (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 this workflow to dump project context, build each section through brainstorming and curation, then verify the doc answers real reader questions before sharing it with stakeholders. ## Quick Start Ask the assistant to guide you through co-authoring a decision doc or technical spec using the structured three-stage workflow.

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?

Start by sharing the document type, audience, and desired impact, then dump all relevant context including background, constraints, and stakeholder concerns. The workflow then builds the doc section by section through brainstorming, curation, and iterative refinement.

How to test if a technical spec is clear to readers?

Use reader testing: generate 5-10 questions a real reader would ask, then have a fresh AI instance with no prior context answer them using only the document. Wrong answers or confusion reveal gaps, ambiguities, and false assumptions to fix.

Can this workflow pull context from Slack or Google Drive?

Yes, if integrations or MCP servers for tools like Slack, Teams, Google Drive, or SharePoint are available, the workflow can read channels and shared documents directly. Without integrations, you paste the relevant content manually.

What document types does this co-authoring workflow support?

It supports structured documents such as technical specs, decision docs, proposals, PRDs, and RFCs. The workflow adapts its section suggestions based on 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 testing adds little value. The structured workflow is most useful for substantial documents that multiple stakeholders will read and act on.