doc-coauthoring

To co-author technical specs or RFCs, you start by providing document context, constraints, and audience. The skill then drafts sections iteratively through targeted questions, brainstorming options, and gap checks before final sharing.

Drafting a decision document collaboratively requires structured context gathering, section-by-section refinement, and reader testing. This approach simulates a fresh reader evaluation to catch ambiguity and assumed knowledge before others review it.

Testing documentation for reader clarity involves simulating a fresh reader evaluation to identify blind spots. The skill prompts you with reader-testing questions to validate comprehension and catch ambiguity before final sharing.

You can use this guided co-authoring process for both starting substantial documentation and revising existing drafts. It applies to technical specs, PRDs, decision docs, RFCs, and proposals by iterating through sections and checking for gaps.

No specific templates are strictly required. The workflow collects document type, audience, constraints, templates, and project context through clarifying questions, allowing you to adapt the structure to your specific RFC, spec, or proposal needs.

You should avoid structured co-authoring for brief, informal notes where staged workflows and section-level brainstorming add unnecessary overhead. It is designed for substantial documentation like PRDs, RFCs, and technical specs requiring reader-testing validation.