skills.rest
boazcstrike
boazcstrikeCOMMUNITY
Explore all skills by this author →
Website𝕏@boazcstrikeGitHub

doc-coauthoring

Guide structured co-authoring of technical specifications, proposals, and decision documents.

3|Updated Dec 23, 2025
Search Tags:#documentation#writing#collaboration#editing#technical writing#drafting
One-click install
npx skills add https://github.com/boazcstrike/opencode --skill doc-coauthoring-boazcstrike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/boazcstrike/opencode/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/boazcstrike/opencode --skill doc-coauthoring-boazcstrike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating well-structured and reader-friendly documents, ensuring clarity and completeness from initial idea to final draft.

Core Features & Use Cases

  • Structured Workflow: Guides users through context gathering, iterative drafting, and reader testing.
  • Content Refinement: Facilitates brainstorming, curation, and surgical editing for each section.
  • Reader Validation: Simulates how a new reader would interpret the document to catch ambiguities and blind spots.
  • Use Case: A product manager needs to write a detailed Product Requirements Document (PRD). This Skill helps them gather all necessary context, structure the PRD logically, draft each section collaboratively, and finally test it to ensure it's clear for engineers and designers.

Quick Start

Use the doc-coauthoring skill to help write a new technical specification document.

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 specifications and proposals collaboratively?▼

Use a structured workflow for co-authoring technical specifications that facilitates context gathering, iterative section refinement through brainstorming, and surgical editing to ensure documentation clarity and completeness.

What is the best way to draft a Product Requirements Document (PRD) collaboratively?▼

Drafting a PRD collaboratively involves gathering necessary context, structuring the document logically, refining each section iteratively, and simulating reader interpretation to ensure it is clear for engineers and designers.

How can I test if my technical writing is clear for the intended audience?▼

Test technical writing clarity by simulating how a new reader would interpret the drafted document, which proactively catches ambiguities, blind spots, and effectiveness issues before final publication.

Can I use this structured drafting workflow for decision documents and various audience types?▼

Yes, the structured drafting workflow supports writing various document types including decision documents and technical specifications while factoring in specific audience considerations for targeted reader validation.

Does collaborative document editing require any specific external dependencies or components?▼

No, collaborative document editing through this structured workflow requires no external dependencies or specific components, allowing you to begin the context gathering and iterative refinement process immediately.

Related Skills

Explore More Content & Communication Skills→
Brennan-WilkersonBrennan-Wilkerson

capture

Parse screenshots, notes, and text into structured contacts, tasks, and ideas for Supabase storage.

Community
Advanced
HahyeonJeonHahyeonJeon

_project-evaluation-aesthetics

Evaluate code deliverables for readability and style issues using defined lenses.

Community
Advanced
whmathews15whmathews15
1

anthropic-doc-coauthoring

Guide collaborative document creation from messy context to reader-ready prose.

Community
Advanced
Codcyber101Codcyber101

doc-coauthoring

Guide structured co-authoring workflows for documentation, proposals, and technical specs.

Community
Basic