doc-coauthoring

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

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/i0switch/yoyaku-tosho --skill doc-coauthoring-i0switch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/i0switch/yoyaku-tosho/tree/main/.github/skills/doc-coauthoring
Command: npx skills add https://github.com/i0switch/yoyaku-tosho --skill doc-coauthoring-i0switch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill guides users through a structured, collaborative workflow to create high-quality documentation, proposals, and decision papers by ensuring clear context, iterative refinement, and reader validation.

Core Features & Use Cases

  • Stage-based guidance across Context Gathering, Refinement & Structure, and Reader Testing.
  • Triggered offer: present a guided workflow when users mention documentation tasks like writing docs, proposals, specs, or decision records.
  • Artifact scaffolding and iterative drafting: generate section outlines, collect clarifying questions, and progressively refine content.
  • Reader testing: validate the doc with a fresh perspective to surface ambiguities and ensure readability.
  • Use Case: a team drafts a technical spec and ADR using the Stage 1 context questions, Stage 2 structured drafting, and Stage 3 reader testing process.

Quick Start

Initiate Stage 1: Context Gathering to collect the document context from the user.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
What is a structured co-authoring workflow for documentation?▼

It guides teams through three stages: Context Gathering to collect scope, Refinement & Structure for iterative drafting, and Reader Testing to validate readability from a fresh perspective.

How do I write technical specs and ADRs collaboratively?▼

Initiate Stage 1 to collect document context, use Stage 2 for artifact scaffolding and iterative drafting of outlines, then apply Stage 3 reader testing to surface ambiguities and ensure readability.

Can I use this workflow for team proposals and decision records?▼

Yes, the workflow applies to writing docs, proposals, specs, and decision records across teams, ensuring clear context, iterative refinement, and reader validation.

How do I validate my documentation for reader clarity?▼

Validate documentation by applying the Reader Testing stage, which analyzes drafts from a fresh perspective to surface ambiguities and ensure the document is reader-friendly.

What is the best way to start drafting a team proposal?▼

Initiate Stage 1: Context Gathering to collect the document context from the user, which generates clarifying questions and artifact scaffolding before iterative drafting begins.