doc-coauthoring

Guide structured co-authoring workflows for drafting and validating documents.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/DFly7/iOS-FastAPI-Supabase-AI --skill doc-coauthoring-dfly7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/DFly7/iOS-FastAPI-Supabase-AI/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/DFly7/iOS-FastAPI-Supabase-AI --skill doc-coauthoring-dfly7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow closes the context gap between authors and reviewers by guiding users through structured context gathering, iterative section drafting, and reader-focused validation so documents work for real readers and downstream reviewers.

Core Features & Use Cases

  • Context Gathering: Ask targeted clarifying questions and accept wide info dumps to capture background, constraints, and stakeholder concerns.
  • Refinement & Structure: Brainstorm options, curate content, and iteratively draft each section with surgical edits and scaffold creation.
  • Reader Testing: Simulate a fresh reader to surface ambiguities and contradictions, then loop back to fix problematic sections.
  • Use Case: Ideal for technical specs, decision docs, PRDs, proposals, and any collaborative writing that requires clear handoff and validation.

Quick Start

Use this workflow to draft a technical spec by answering context questions, choosing section priorities, and iteratively refining each section until reader testing passes.

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 specs to ensure reader clarity for downstream reviewers?

Iterative document drafting uses targeted clarifying questions to capture context, followed by staged section refinement and reader testing to validate clarity and fix ambiguities before handoff.

What is the best way to structure collaborative writing for decision docs and proposals?

The best way to structure collaborative writing for decision docs is to use staged context gathering, iterative section drafting with artifact management, and reader testing to validate clarity and resolve contradictions.

Can I use this workflow to draft a PRD from unstructured information dumps?

Yes, this workflow accepts wide info dumps to capture background and constraints, then iteratively drafts PRD sections and simulates a fresh reader to validate clarity before finalizing the document.

How does reader testing work to identify contradictions in documentation?

Reader testing works by simulating a fresh reader to surface ambiguities and contradictions within the drafted sections, then looping back to fix problematic areas and validate overall document readability.

Do I need any specific tools or dependencies to run this iterative editing workflow?

No specific dependencies are required to run this iterative editing workflow; it operates independently to guide context gathering, artifact management, and reader testing for your documentation.