---
title: Doc Coauthoring
category: product
entity_type: skill
price: $15
canonical: https://forgehouse.ai/skills/doc-coauthoring/
lang: en
hreflang_alt: https://forgehouse.ai/tr/skiller/doc-coauthoring/
last_updated: 2026-06-20
---

# Doc Coauthoring

> Guide users through a structured workflow for co-authoring documentation.

Guides you through a structured, three-stage workflow for co-authoring documentation, proposals, specs, and decision docs with an AI partner. It moves from context gathering, to section-by-section refinement, to reader testing with a fresh AI instance that catches blind spots before others see them. Turns a blank page into a clear document that actually works for its readers.

## Use cases
- Writing a product requirements document (PRD) or design doc
- Drafting a proposal, RFC, or technical specification
- Building a decision document section by section
- Transferring messy context to an AI partner efficiently
- Testing a draft for ambiguity and false assumptions before sharing
- Refining each section through brainstorming and surgical edits

## Benefits
- Go from blank page to finished doc with a guided, repeatable process
- Catch blind spots before colleagues do via fresh-reader testing
- Produce documents that read clearly for their intended audience
- Save time by refining sections surgically instead of rewriting from scratch

## What’s included
- Stage 1 context-gathering workflow with clarifying-question prompts
- Stage 2 section-by-section refinement with brainstorm, curate, draft, and edit steps
- Stage 3 reader-testing with a fresh AI instance to surface gaps
- Pyramid-principle and progressive-disclosure structuring guidance
- Quality checks for redundancy, contradictions, and generic filler
- Final-review checklist covering facts, links, and intended impact

## Who it’s for
Anyone who writes substantial documents (PRDs, specs, proposals, decision docs) and wants them to land clearly with readers.

## How it runs
Writing together runs in three stages: the skill interrogates your context first, scaffolds the document section by section while you curate every brainstorm, then hands the draft to a cold reader to prove it stands alone.
1. Stage 1, context gathering: asks five meta questions (doc type, audience, desired impact, template, constraints), then invites a full info dump including team threads and linked docs, and closes the gap with 5 to 10 numbered clarifying questions you can answer in shorthand.
2. Stage 2 opens with a scaffold: agrees the section structure, creates the document with placeholder text for every section, and starts with whichever section has the most unknowns rather than the easiest one.
3. Each section runs its own micro-loop: clarifying questions, a brainstorm of 5 to 20 candidate points, your keep/remove/combine curation with brief justifications it learns from, a gap check, then the draft, written by surgical edits rather than reprinting the whole document.
4. After three consecutive iterations with no substantial change it flips to pruning: asks what can be removed without losing information, and near completion re-reads the entire document for flow, contradictions and generic filler.
5. Stage 3, reader testing: predicts 5 to 10 questions real readers would ask, hands the document to a fresh instance with zero conversation context, scores what that reader got right or wrong, and loops the failures back into refinement until the cold reader answers everything correctly.

## FAQ
### Does this only fit engineering specs, or also a proposal or decision doc?
The three-stage flow works for PRDs, proposals, RFCs and decision docs alike. The structure is about thinking, not a single document template.

### What does the fresh-reader test actually do that I can't do myself?
A clean AI instance reads the draft with no memory of the conversation, so it catches assumptions you no longer notice. It surfaces the gaps a reader will hit before a real reviewer does.

### Will it write the whole document, or do I still do the work?
It co-authors: you bring the substance and decisions, it structures, refines and pressure-tests. It is a thinking partner, not a button that produces a finished doc from nothing.

## Price
$15, one-time, no subscription. VAT included.

Related guide: [Building a multilingual AI content pipeline](https://forgehouse.ai/guides/ai-content-pipeline/)