doc-coauthoring

Guides users through a three-stage workflow for co-authoring documentation.

Updated Jan 28, 2026

Search Tags:#workflow #documentation #artifact #coauthoring #reader-testing #clarifying-questions #stage-gate

Ready to run

npx skills add https://github.com/apostolos-geyer/StoliStack --skill doc-coauthoring-apostolos-geyer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/apostolos-geyer/StoliStack/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/apostolos-geyer/StoliStack --skill doc-coauthoring-apostolos-geyer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through a structured workflow for co-authoring documentation, enabling efficient context transfer, iterative refinement, and verification that the final doc works for readers.

Core Features & Use Cases

Context Gathering: collect all relevant information and clarify requirements.
Refinement & Structure: iteratively build and organize sections through brainstorming and editing.
Reader Testing: validate the document's clarity by simulating reader questions and feedback.
Trigger-based offers: detects when users mention writing docs, proposals, specs, RFCs, or design docs, and offers the workflow.
Artifact & feedback loops: optional creation of scaffolds and structured feedback to improve later sections.

Quick Start

Initiate the Doc Co-Authoring Workflow and guide me through Context Gathering, Refinement & Structure, and Reader Testing.

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 documentation using a structured workflow?▼

To co-author technical documentation, use a structured workflow that guides you through Context Gathering, Refinement & Structure, and Reader Testing to iteratively build proposals, specs, or RFCs and verify clarity for readers.

What is the best way to write an RFC with iterative feedback loops?▼

The best way to write an RFC is to apply a stage-gate process that enforces clarifying questions during context gathering and uses structured feedback loops during iterative drafting to refine the artifact before reader testing.

How can I test if my technical spec is clear for readers?▼

You can test if a technical spec is clear for readers by simulating reader questions and feedback during a dedicated Reader Testing stage, which validates the document's clarity and ensures it is reader-ready.

Does the documentation coauthoring workflow support creating scaffolds for proposals?▼

Yes, the documentation coauthoring workflow supports optional artifact creation, allowing you to generate scaffolds and structured feedback to improve later sections of your proposals or design docs.

When do I need a stage-gate process for writing design docs?▼

You need a stage-gate process for writing design docs when you want to enforce structured context gathering, iterative refinement, and reader testing to ensure the final artifact effectively communicates complex technical information.

Can I use this workflow to write proposals and technical specs?▼

Yes, you can use this workflow to write proposals and technical specs because it applies a structured co-authoring process across various documentation artifacts, including RFCs and design docs, to ensure reader-ready output.