doc-coauthoring

Guide structured co-authoring of technical specs and decision documents.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Estom/aiflex --skill doc-coauthoring-estom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Estom/aiflex/tree/main/skills-repo/arthropic-skills/doc-coauthoring
Command: npx skills add https://github.com/Estom/aiflex --skill doc-coauthoring-estom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams or individuals start substantial writing tasks they often fail to transfer full context, iterate effectively, and verify the document actually works for readers; this workflow structures context gathering, iterative drafting, and reader testing to produce clear, usable documents.

Core Features & Use Cases

  • Context Gathering: Elicits background, constraints, audience, templates, and a comprehensive info dump plus 5–10 clarifying questions to close knowledge gaps.
  • Refinement & Structure: Builds section-by-section scaffolds, brainstorms options, curates content, drafts text, and performs surgical iterative edits while tracking preferences.
  • Reader Testing: Simulates a fresh reader to predict questions, run tests (via sub-agents when available), detect ambiguities or assumptions, and loop fixes back into drafting.
  • Use Case: Ideal for drafting technical specs, decision documents, PRDs, proposals, or any collaborative document that must be clear to new readers.

Quick Start

Help me co-author a decision document by guiding context gathering, iteratively drafting each section, and then testing the doc as a fresh reader.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I co-author technical specs and ensure the document is clear for new readers?

To co-author technical specs effectively, you need a workflow that elicits background context, scaffolds section-by-section drafting, and runs reader testing to surface ambiguities and loop fixes back into the text.

What is the best way to structure collaborative writing for decision documents?

Structuring collaborative writing for decision documents involves collecting comprehensive context, generating clarifying questions, and refining text through iterative edits to ensure the final proposal is clear and usable.

How do you test documentation for ambiguities before publishing?

You test documentation for ambiguities by simulating a fresh reader perspective, which predicts reader questions, detects assumptions, and loops identified fixes back into the drafting phase.

Can I use this structured workflow for drafting PRDs and proposals?

Yes, this structured workflow applies to drafting PRDs and proposals, as it handles context gathering, section-by-section scaffolding, and iterative refinement for any collaborative document.

Why does my team's collaborative writing often fail to transfer full context?

Collaborative writing fails to transfer full context when teams skip structured context gathering, which should elicit background, constraints, audience, and generate clarifying questions to close knowledge gaps.

When should I not use an iterative editing workflow for documentation?

Avoid using an iterative editing workflow for documentation when the writing task is trivial, requires no collaborative context transfer, or does not need fresh reader testing to verify document usability.