doc-coauthoring

Guides structured co-authoring of specs, proposals, PRDs, RFCs, and decision documents.

52|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Immortalqx/my_codex_skills --skill doc-coauthoring-immortalqx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Immortalqx/my_codex_skills/tree/main/doc-coauthoring
Command: npx skills add https://github.com/Immortalqx/my_codex_skills --skill doc-coauthoring-immortalqx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-form documents like specs, proposals, and decision docs often fail not because of grammar but because of missing context, weak structure, or unclear reader expectations. This Skill provides a staged workflow that gathers context, scaffolds the document, drafts section by section, and validates the result with a cold-reader test before handoff. ## Core Features & Use Cases - Context Gathering: Collects document type, audience, target decision, constraints, and source material, then asks focused clarifying questions before drafting. - Scaffolding and Section Drafting: Creates a local Markdown scaffold with placeholders, then drafts each section through a clarify-brainstorm-curate-draft-refine loop. - Cold-Reader Test: Generates realistic reader questions and checks whether a fresh reader can answer them from the document alone, fixing gaps iteratively. - Use Case: A product manager needs an RFC for a new API design. The Skill interviews them about the problem and audience, builds a section scaffold, drafts each section collaboratively, and runs a reader test so reviewers can understand the proposal without extra explanation. ## Quick Start Use the doc-coauthoring skill to help me plan and draft a decision document for migrating our service to a new database, section by section.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I write a technical design doc with an AI assistant?

Use a staged co-authoring workflow: first gather context about the problem, audience, and decision, then create a section scaffold, draft each section through clarifying questions, and finish with a cold-reader test. This Skill implements exactly that process for specs, RFCs, and design docs.

How to structure a decision document or RFC?

A decision doc typically covers context, problem, options, recommendation, risks, and rollout, while a technical spec covers goal, requirements, design, edge cases, rollout, and open questions. The Skill proposes a minimal structure matching your document type or follows your existing template.

Can this workflow produce Word documents or slides?

The workflow is format-agnostic and uses plain Markdown by default. If the deliverable must be a Word document, slide deck, or spreadsheet, the Skill hands off file-format work to the docx, pptx, or xlsx skills after the structure is stable.

What is a cold-reader test for documents?

A cold-reader test checks whether a fresh reader can answer key questions using only the document, without context from the drafting conversation. The Skill generates 5 to 10 realistic reader questions and uses a fresh subagent or a manual review to find gaps, then fixes the responsible sections.

When should I not use a structured co-authoring workflow?

Skip it for short or informal writing where structure and reader validation add no value, or when you already know exactly what to write. The Skill explicitly supports abandoning the workflow and drafting freeform if the user prefers.