doc-coauthoring

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

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Xinm123/MyRecall --skill doc-coauthoring-xinm123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Xinm123/MyRecall/tree/main/openrecall/.trae/skills/doc-coauthoring
Command: npx skills add https://github.com/Xinm123/MyRecall --skill doc-coauthoring-xinm123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide users through a structured co-authoring workflow for documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Core Features & Use Cases

  • Stage 1: Context Gathering — gather context with targeted questions to close knowledge gaps.
  • Stage 2: Refinement & Structure — iteratively draft sections, refine content, and align with audience needs.
  • Stage 3: Reader Testing — validate the document by testing with a fresh perspective to surface blind spots.
  • Trigger & initial offer: present a structured workflow when the user indicates they are starting a documentation task; if accepted, move to Stage 1.

Quick Start

Initiate the structured co-authoring workflow for your document task. If the user accepts, proceed to Stage 1: Context Gathering. Then ask the initial questions to gather context, and outline the plan for the next steps.

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 specifications with a team?

Co-author technical specifications by following a structured workflow that gathers context, iteratively refines content, and tests the document with readers to surface blind spots.

What is the best way to draft decision records collaboratively?

Drafting decision records collaboratively is best handled by applying defined stages, prompts, and templates to coordinate the team, align with audience needs, and refine the structure.

How do I start writing proposals through structured iteration?

Start writing proposals by triggering the workflow, accepting the initial offer, and proceeding to context gathering where targeted questions close knowledge gaps before outlining next steps.

Can I use templates to guide documentation refinement?

Yes, you can use templates to guide documentation refinement, relying on them alongside prompts and artifact outputs to iteratively draft sections and align content with audience needs.

Does reader testing help validate structured documentation?

Reader testing validates structured documentation by testing the draft with a fresh perspective, which surfaces blind spots and verifies that the technical specs or proposals work for the audience.