doc-coauthoring

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

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/SESELOVSKYDarian/Vase --skill doc-coauthoring-seselovskydarian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/SESELOVSKYDarian/Vase/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/SESELOVSKYDarian/Vase --skill doc-coauthoring-seselovskydarian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, or specs alone often produces documents full of blind spots, missing context, and unclear sections that confuse readers. This Skill provides a structured three-stage workflow that turns document writing into a guided collaboration, ensuring the final doc actually works for its intended audience. ## Core Features & Use Cases - Context Gathering: Collects background, audience, constraints, and organizational context through targeted questions before any drafting begins. - Section-by-Section Refinement: Brainstorms 5-20 options per section, curates them with the user, then drafts and iteratively refines each section using surgical edits. - Reader Testing: Validates the finished document with a fresh, context-free reviewer (sub-agent or manual test) to catch ambiguities, false assumptions, and contradictions. - Use Case: A product manager needs to write a decision doc for a migration plan. The workflow gathers stakeholder context, drafts each section through curated brainstorming, then tests the doc with a fresh reader to confirm it stands on its own. ## Quick Start Ask the assistant to guide you through writing a decision doc 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?

Use a structured co-authoring workflow: first dump all relevant context while answering clarifying questions, then build the doc section by section through brainstorming and curation, and finally test it with a fresh reader to catch blind spots before sharing.

How to structure a technical spec or proposal document?

Start by defining the doc type, audience, and desired impact, then agree on 3-5 sections appropriate for the document type. Draft the section with the most unknowns first, refine each through iterative feedback, and leave summary sections for last.

What is reader testing for documentation?

Reader testing validates a document by having a fresh reviewer with no prior context answer predicted reader questions. It catches ambiguities, assumed knowledge, and contradictions that authors miss because they already understand the subject.

Can this workflow use templates or existing documents?

Yes, you can provide a template file or link to an existing shared document at the start. The workflow reads the current state, follows the template structure, and can flag images missing alt-text for accessibility.

When should I skip the structured doc workflow?

Skip it for short, low-stakes writing where a full three-stage process adds overhead. The workflow is designed for substantial documents like specs, RFCs, and proposals where reader clarity matters; you can always choose freeform drafting instead.