documentation-authoringlisted

# Documentation Authoring Master Expert guidance for creating structured, high-quality documentation across all types of technical and business documents. - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## Activation Conditions Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below. **Trigger Conditions:** - User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up" - User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC" - User asks to "create an implementation plan", "document requirements", "plan a feature" - Creating technical specifications or business requirements - Starting a new product or feature development cycle - Translating vague ideas into concrete technical specifications - Stakeholders need unified "source of truth" for project scope ## Part 2: Context Gathering ### Initial Questions Start by asking for meta-context about the document: 1. **What type of document is this?** - Technical spec, decision doc, proposal, RFC, PRD, knowledge base 2. **Who's the primary audience?** - Developers, executives, stakeholders, end-users? Understanding affects tone and depth 3. **What's the desired impact when someone reads this?** - Make a decision, implement a feature, understand a concept? 4. **Is there a template or specific format to follow?** - Company templates, industry standards, regulatory req