doc-coauthoring

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

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/gtbauke/bj-utils --skill doc-coauthoring-gtbauke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/gtbauke/bj-utils/tree/main/.agent/skills/doc-coauthoring
Command: npx skills add https://github.com/gtbauke/bj-utils --skill doc-coauthoring-gtbauke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and specs alone often produces documents full of blind spots, missing context, and 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, constraints, and stakeholder context through structured questions and info dumps before any 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 reader to catch ambiguities, false assumptions, and contradictions. - Use Case: A product manager needs to write a decision doc for a migration plan. The Skill gathers organizational context, drafts each section through brainstorming and curation, then tests the doc with a fresh reader to ensure teammates can understand it without extra explanation. ## Quick Start Ask the assistant to guide you through writing a decision doc or technical spec using the structured co-authoring 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?▼

Start by sharing the document type, audience, and desired impact, then dump all relevant context. The workflow brainstorms options per section, drafts based on your selections, and tests the final doc with a fresh reader to catch gaps.

What is the best workflow for drafting technical specs collaboratively?▼

A three-stage approach works well: gather context through clarifying questions, build each section via brainstorming and iterative edits, then validate with reader testing. This ensures the spec works for readers who lack your background knowledge.

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 team channels and shared documents. Without integrations, you can paste the relevant content manually into the conversation.

How does reader testing catch documentation blind spots?▼

Reader testing gives the finished document to a fresh reviewer with no prior context, then asks realistic reader questions. Wrong answers, ambiguities, or assumed knowledge reveal gaps that get fixed through another refinement pass.

When should I skip the structured workflow and write freeform?▼

Freeform writing suits short or low-stakes documents where reader ambiguity carries little risk. The structured workflow is better for substantial docs like RFCs, proposals, and specs that many stakeholders will read and act on.