Guide collaborative documentation creation with structured questioning and reader-style validation.
npx skills add https://github.com/mykcs/myk-skills --skill doc-coauthoring-mykcs
Please help me install this Agent Skill. Skill: doc-coauthoring Source: https://github.com/mykcs/myk-skills/tree/main/doc-coauthoring Command: npx skills add https://github.com/mykcs/myk-skills --skill doc-coauthoring-mykcs
It helps you produce collaborative documentation or technical specs that are complete, well-structured, and easy for new readers to understand.
Tell the skill what type of document you are writing, who the audience is, and what format (if any) you want to follow.
High-intent search queries and answers about installing and using this skill.
Draft technical specs by gathering missing context first, refining structure section-by-section, and validating readability with a blind-reader test. This staged editorial workflow surfaces trade-offs and audience assumptions to reduce ambiguity in PRDs and design docs.
Structure RFC-style proposals by guiding section-by-section drafting with iterative edits and option brainstorming. Curation builds the document incrementally while making constraints and trade-offs explicit for the audience.
Yes, validate a PRD using the final blind-reader validation loop. A fresh reader perspective catches hidden assumptions and ambiguities, ensuring the document reads clearly and lands well before stakeholder distribution.
Surface missing constraints in design docs through structured questioning before writing. Context gathering prompts you to articulate background, trade-offs, and audience assumptions explicitly, reducing omission risks later.
Yes, this collaborative documentation process works for technical writing including specs, proposals, and decision records. It applies a staged workflow of context gathering, iterative drafting, and reader testing to handle complex trade-offs.
Iterative section-by-section drafting requires upfront context gathering and a final reader-testing loop, meaning it demands more stages than direct writing. Skipping the validation loop risks leaving hidden assumptions uncaught in the document.
ljucaskGenerates a project charter and assumptions risk register for new product planning.
rvdbreemenGuide collaborative documentation through staged drafting and reader-testing checks.
nanorepublicaEnforce standardized test-writing guidelines within Claude Code workflows.
datascienceworld-kanGuide structured document co-authoring through context gathering, refinement, and reader testing.
