doc-coauthoring

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill doc-coauthoring-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill doc-coauthoring-cyrus-pinto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and specs alone often produces documents full of blind spots, missing context, and unclear sections that confuse readers. This Skill structures the co-authoring process so the final document actually works for its intended audience. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through structured questions and info dumps before drafting begins. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates them with the user, then drafts and iteratively edits each section. - Reader Testing: Validates the finished document with a fresh, context-free reviewer to catch 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 curated brainstorming, and 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 AI assistance?

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

How to structure a technical spec or proposal document?

Start by identifying the doc type, audience, and desired impact, then agree on 3-5 sections appropriate for the document. Begin drafting with the section that has the most unknowns, typically the core proposal or technical approach, and leave summaries for last.

What is reader testing for documentation?

Reader testing validates a document by having a fresh reviewer with no prior context answer realistic reader questions. It catches ambiguity, false assumptions, and contradictions that authors miss because they already understand the material.

Can this workflow use content from Slack or Google Docs?

Yes, if integrations or MCP connectors are available, the workflow can pull context directly from messaging channels and shared documents. Without integrations, you paste the relevant content manually into the conversation.

When should I skip the structured doc workflow?

Skip it for short or low-stakes writing where three stages of iteration add unnecessary overhead. The workflow is designed for substantial documents like specs, RFCs, and decision docs where reader clarity matters.