Guide teams through a three-stage documentation co-authoring workflow.
npx skills add https://github.com/Leon0050/m_pro --skill doc-coauthoring-leon0050
Please help me install this Agent Skill. Skill: doc-coauthoring Source: https://github.com/Leon0050/m_pro/tree/main/llm/trae/doc-coauthoring Command: npx skills add https://github.com/Leon0050/m_pro --skill doc-coauthoring-leon0050
Guides teams through structured co-authoring of documentation, ensuring context is captured, structure is refined, and readers are tested before publication.
Begin with Stage 1: Context Gathering by prompting the user for document type, audience, and constraints to kick off the workflow.
High-intent search queries and answers about installing and using this skill.
Streamline collaborative writing for technical documentation by guiding teams through a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This ensures stakeholders align on audience and constraints before iteratively refining content and validating readability with an unbiased perspective.
The best way to co-author design docs and proposals is to enforce an artifact-based drafting process. This approach iteratively organizes content, sections, and rationale to capture context, refine structure, and test readers before publication, ensuring clarity and alignment across all stakeholders.
Start a structured documentation workflow for a technical spec by initiating Stage 1: Context Gathering. Prompt the team for the document type, target audience, and project constraints to kick off the process and align stakeholders before drafting begins.
Use a structured co-authoring workflow for technical specs, proposals, design docs, and decision documents that require collaborative input and iterative refinement. It is essential when you need to ensure context capture, content clarity, and reader testing before publication.
Reader testing improves the documentation refinement process by validating readability and coverage with a fresh, unbiased perspective. This final stage ensures the structured document is clear and comprehensive for the target audience before publication, reducing misinterpretation.
Owl-ListenerDefine and document a design brief with problem space, audience, constraints, and success criteria.
workinprogress-aiManages pair-programming sessions with GitHub-issue-based implementation plans and approval gates.
MunreaderCreate and edit Word documents with styles, comments, and track changes.
coolbeevipConvert structured PRDs into human-readable alignment materials for stakeholder review.
