doc-coauthoring

Guide structured co-authoring of documentation through context gathering, iterative refinement, and reader validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps users produce high-quality documentation by turning an open-ended writing task into a structured, collaborative workflow that iterates on clarity, completeness, and readability for others.

Core Features & Use Cases

  • Context Gathering with Clarifying Questions: Guides the user to provide all relevant meta-context (audience, purpose, constraints, templates) and encourages dumping supporting background.
  • Refinement & Section-by-Section Drafting: Builds the document through ordered stages—clarify each section, brainstorm options, curate what to keep/remove/combine, draft, and refine iteratively.
  • Reader Testing for Blind Spots: Verifies the document “works for readers” by predicting likely reader questions and testing with a fresh Claude instance to catch ambiguity and missing assumptions.
  • Use Case: When starting a PRD, RFC, decision doc, or technical spec, the skill helps quickly converge on a coherent draft that others can understand when pasted into their own tools.

Quick Start

Tell the AI you want to create a decision doc for a new feature and ask it to run the Doc 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 co-author technical specs and decision docs to reduce ambiguity for readers?

Co-author technical specs and decision docs by using a structured workflow that gathers context, iteratively refines sections, and runs reader-focused validation to reduce ambiguity. This stage-based approach ensures documents are clear and complete.

What is the best way to draft a PRD or RFC collaboratively from scratch?

Drafting a PRD or RFC collaboratively involves a stage-based workflow: gathering meta-context and background, refining section-by-section through brainstorming and curating, and testing with a fresh instance to catch missing assumptions.

How do I test my documentation for blind spots before sharing it?

Test documentation for blind spots by running reader-focused validation that predicts likely reader questions and performs a no-context test with a fresh instance to catch ambiguity and missing assumptions.

Can I use this structured writing workflow with partially shared materials and templates?

Yes, you can use this structured writing workflow with partially shared materials. It guides you to provide relevant meta-context like audience, purpose, constraints, and templates before iteratively drafting the document.

What are the limitations of iterative refinement for technical documentation?

Iterative refinement for technical documentation requires explicit stage-based workflows and active participation in clarifying sections, meaning it may not suit users seeking instant, single-prompt generation without collaborative editing.