Can I use my existing team documents as context?

Yes. If you have MCP integrations enabled (like Google Drive or Slack), the skill can pull context directly to inform the drafting process.

How does the 'Reader Testing' phase work?

It invokes a fresh Claude instance without your conversation context to read the draft. This identifies what a 'cold' reader might find confusing or missing.

What types of documents does this skill handle best?

It is optimized for structured documents such as technical specs, PRDs, RFCs, decision logs, and project proposals.

Why is a structured workflow better than a single prompt?

A structured workflow prevents 'hallucinated' context and generic filler by ensuring every section is brainstormed, curated, and validated against your specific goals.

Doc Co-Authoring Workflow

Name: Doc Co-Authoring Workflow
Author: lingxling

bylingxling

•

学習とドキュメンテーション

Guides users through a structured, three-stage process for creating high-quality technical documentation and proposals.

This skill transforms Claude into an expert co-author for technical documents, proposals, and specifications. It follows a rigorous workflow involving deep context gathering to align on objectives, iterative section-by-section drafting with brainstorming, and a unique 'Reader Testing' phase where sub-agents evaluate the draft for clarity and blind spots. It is ideal for developers and product managers who need to produce clear, impact-driven documentation like PRDs, RFCs, and architecture decision records without the stress of starting from a blank page.

主な機能

01Iterative section-by-section brainstorming and curation

02Surgical document refinement using persistent file edits or Artifacts

03Automated 'Reader Testing' using sub-agents to find blind spots

0439 GitHub stars

05Structured three-stage workflow: Context, Refinement, and Testing

06Deep context gathering with MCP integration support

ユースケース

01Writing high-stakes project proposals or architecture decision logs

02Creating Product Requirement Documents (PRDs) with clear impact

03Drafting complex Technical Design Docs or RFCs

主な機能

01Iterative section-by-section brainstorming and curation

02Surgical document refinement using persistent file edits or Artifacts

03Automated 'Reader Testing' using sub-agents to find blind spots

0439 GitHub stars

05Structured three-stage workflow: Context, Refinement, and Testing

06Deep context gathering with MCP integration support

ユースケース

01Writing high-stakes project proposals or architecture decision logs

02Creating Product Requirement Documents (PRDs) with clear impact

03Drafting complex Technical Design Docs or RFCs