Guide structured co-authoring from rough ideas to reader-ready documentation.
npx skills add https://github.com/lth0/codexSkill --skill doc-coauthoring-lth0
Please help me install this Agent Skill. Skill: doc-coauthoring Source: https://github.com/lth0/codexSkill/tree/main/skills/agents/doc-coauthoring Command: npx skills add https://github.com/lth0/codexSkill --skill doc-coauthoring-lth0
It prevents documentation from being written in a way that only works for the author, by guiding co-authors through structured context gathering, iterative drafting, and a reader-focused validation pass.
Use cases: PRDs, design docs, RFCs, decision docs, technical specs, proposals, and other structured writing where correctness and readability for others matter.
Use this workflow when you’re starting a doc and ask for a “co-authoring workflow” to draft a reader-ready proposal using stages for context gathering, structured refinement, and reader testing.
High-intent search queries and answers about installing and using this skill.
To co-author technical specs effectively, you need a structured workflow that gathers context through clarifying questions, drafts sections iteratively, and validates results with reader testing to catch ambiguity.
Drafting a PRD without missing context requires starting with context gathering, where you define the audience, goals, and constraints before building the document section-by-section with iterative refinement.
Validating decision docs for blind spots involves performing a reader testing pass, which tests the drafted document against a fresh perspective to identify and fix missing assumptions or ambiguity.
Yes, you can use this co-authoring workflow for writing proposals and RFCs, as it applies to any structured writing task like technical specs, PRDs, and decision docs where correctness and readability matter.
Iterative section refinement for proposal writing works by brainstorming options for each section, allowing you to curate what to keep, and then drafting and refining the content through successive edits until the section is polished.
Technical documentation often only makes sense to the author because it lacks a structured reader-focused validation pass to identify missing context, ambiguity, and assumptions that a fresh reader would need clarified.
CommonCapitalGuide users through a structured workflow for co-authoring technical and business documentation.
devtitusGuide structured documentation co-authoring through context gathering, refinement, and reader testing.
curiositechImplement WebSocket communication with OT/CRDT conflict resolution and presence awareness.
aws-samplesGuide structured co-authoring workflows for drafting documentation and proposals.
