doc-coauthoring

Coordinates context gathering, iterative refinement, and reader testing for structured documents.

Updated Nov 9, 2025
One-click install
npx skills add https://github.com/xu-mengnan/bilibili --skill doc-coauthoring-xu-mengnan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/xu-mengnan/bilibili/tree/main/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/xu-mengnan/bilibili --skill doc-coauthoring-xu-mengnan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the inefficiency and inconsistency of ad-hoc document writing, which often leads to missing context, unclear messaging, and documents that fail to meet the needs of their intended readers.

Core Features & Use Cases

  • 3-Stage Guided Workflow: Structured process covering context gathering, iterative section refinement, and reader testing to ensure documents are complete and clear.
  • Context Alignment: Helps authors capture all relevant background, stakeholder context, tradeoffs, and constraints before drafting to avoid knowledge gaps.
  • Reader Validation: Tests drafted content with a fresh AI instance to catch blind spots, ambiguities, and assumptions that authors may miss.
  • Use Case: Ideal for teams creating technical design documents, product proposals, decision records, PRDs, and RFCs that need to be understood by cross-functional stakeholders.

Quick Start

Use the doc-coauthoring skill to guide me through creating a decision record for our new payment processing integration, following the full 3-stage structured workflow.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I structure a technical specification to ensure cross-functional stakeholders understand it?

A structured end-to-end document authoring workflow ensures clear, reader-ready technical specifications by coordinating context gathering, iterative section refinement, and reader validation to eliminate knowledge gaps before publication.

What is the best way to capture context and constraints before drafting a product proposal?

The best way to capture context before drafting a product proposal is applying a context alignment phase to collect relevant background, stakeholder context, tradeoffs, and constraints, avoiding knowledge gaps before iterative section refinement begins.

How do I validate a drafted RFC for blind spots and reader assumptions?

You validate a drafted RFC for blind spots and reader assumptions by executing a reader validation stage, testing drafted content with a fresh AI instance to catch ambiguities and assumptions authors missed.

Can I use this structured workflow for writing both PRDs and decision records?

Yes, you can use this structured workflow for writing both PRDs and decision records, as the 3-stage guided process applies broadly to authoring structured professional documents including technical designs and RFCs.

Why does ad-hoc document writing fail to meet the needs of intended readers?

Ad-hoc document writing fails to meet intended reader needs because it causes inefficiency, inconsistency, missing context, and unclear messaging, which a structured 3-stage workflow prevents by refining sections iteratively before publication.