doc-coauthoring

Guide structured co-authoring of technical documents through iterative drafting and reader testing.

4|1|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/rm2thaddeus/Aitor_Skills --skill doc-coauthoring-rm2thaddeus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/rm2thaddeus/Aitor_Skills/tree/main/doc-coauthoring
Command: npx skills add https://github.com/rm2thaddeus/Aitor_Skills --skill doc-coauthoring-rm2thaddeus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating structured documents like proposals, technical specs, and decision docs, ensuring clarity and reader comprehension.

Core Features & Use Cases

  • Structured Workflow: Guides users through context gathering, iterative refinement, and reader testing.
  • Contextual Understanding: Actively asks clarifying questions to build a comprehensive understanding of the document's purpose and content.
  • Iterative Drafting: Facilitates section-by-section content creation, brainstorming, and editing.
  • Reader Validation: Simulates reader interaction to identify and address potential ambiguities or blind spots.
  • Use Case: A product manager needs to draft a new PRD. This Skill helps them gather all necessary background, brainstorm sections, draft the content iteratively, and finally test it from a reader's perspective before wider distribution.

Quick Start

Use the doc-coauthoring skill to help write a new technical specification document.

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 through an iterative workflow?

To draft technical specifications or proposals, this Skill guides you through context gathering, iterative section-by-section drafting, and reader validation. It actively asks clarifying questions to build comprehensive understanding before facilitating the editing process.

What is the best way to structure a technical specification or proposal collaboratively?

The best way to structure technical specifications collaboratively is through an iterative workflow that gathers context, drafts section by section, and simulates reader testing. This approach identifies ambiguities and blind spots to ensure reader comprehension before distribution.

Can I use this workflow to draft a new product requirements document from scratch?

Yes, you can use this workflow to draft a new product requirements document from scratch. It helps product managers gather necessary background, brainstorm sections, iteratively draft content, and test the document from a reader's perspective before wider distribution.

Does the co-authoring process support brainstorming and content scaffolding?

Yes, the co-authoring process supports brainstorming and content scaffolding through optional artifact creation. It facilitates section-by-section content creation while actively asking clarifying questions to comprehensively understand the document's purpose.

How does reader validation work when writing decision docs?

Reader validation for decision docs simulates reader interaction to identify and address potential ambiguities or blind spots. This ensures the final document achieves clarity and reader comprehension before wider distribution.