collaborative-docs

Guide iterative document drafting through structured feedback and versioned revisions.

Updated Aug 12, 2024

Search Tags:#feedback #documentation #collaboration #guidance #iteration #document-editing

Ready to run

npx skills add https://github.com/andreasphil/ris-utils --skill collaborative-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: collaborative-docs
Source: https://github.com/andreasphil/ris-utils/tree/main/ris-search/claude/skills/collaborative-docs-skill
Command: npx skills add https://github.com/andreasphil/ris-utils --skill collaborative-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative documentation is often slow and error-prone when working with users to draft, revise, and restructure concept notes, strategy documents, technical specs, or guides through back-and-forth conversations instead of delivering a finished document upfront.

Core Features & Use Cases

Guided iterative drafting: facilitates multiple rounds of refinement by capturing user feedback and updating content accordingly.
Structure-first collaboration: starts with an outline and expands into sections while preserving user intent and voice.
Feedback architecture: provides concise, actionable edits and tracks changes over iterations for traceability.

Quick Start

Ask about the document purpose and audience, draft a clear outline, write the initial draft, and invite targeted feedback for iterative refinement.

Frequently Asked Questions about collaborative-docs

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

FAQPage Schema

How do I collaboratively refine a technical spec through iterative feedback?▼

You collaboratively refine a technical spec through a structured workflow of context gathering, outlining, drafting, and targeted feedback capture across multiple iterations, producing versioned revisions that trace changes while preserving user intent.

What is the best way to draft strategy docs with multiple rounds of user edits?▼

The best way to draft strategy docs with user edits is a structure-first collaboration approach that starts with a clear outline, expands into sections, and invites targeted feedback to drive iterative refinement while tracking actionable changes.

How does iterative document-editing handle changes without losing original voice?▼

Iterative document-editing preserves original voice by capturing initial context and user intent, then applying concise, actionable edits through versioned revisions rather than rewriting content wholesale during feedback rounds.

Can I use this approach for both concept docs and technical guides?▼

Yes, this approach applies to concept docs, strategy docs, technical specs, and guides. It facilitates back-and-forth refinement across multiple iterations for any document type requiring collaborative editing and user feedback.

Do I need any specific tools to start collaborative documentation?▼

No specific tools are required to start collaborative documentation. The process works by asking about document purpose and audience, drafting a clear outline, writing an initial draft, and inviting targeted feedback for iterative refinement.

When should I avoid iterative collaboration for document drafting?▼

You should avoid iterative collaboration for document drafting when you need to deliver a finished document upfront rather than capturing feedback and updating content through back-and-forth refinement across multiple rounds of conversation.