When writing technical documentation that must influence decisions, teach others, or be a permanent record.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Developer Productivity & Career - Use case: Technical Writing Toolkit - Source task: - Help me write {{type_of_technical_document_rfc_adr_post_mortem_onboarding_guide_}} about {{topic}}. Include: - 1. the standard structure for this document type - 2. a complete draft of the document based on: {{describe_the_context}} - 3. common mistakes in this document type and how to avoid them - 4. how to make it scannable for a busy engineering audience - 5. review checklist before publishing # Goal Document type structure, complete draft, common mistake guide, scannability tips, and a pre-publish checklist. # Constraints - Produce a complete, usable first draft in one response. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Document type structure, complete draft, common mistake guide, scannability tips, and a pre-publish checklist.
{{double-curly}} with your real context.When writing technical documentation that must influence decisions, teach others, or be a permanent record.
An RFC that isn't read doesn't exist — write the executive summary first and make sure it stands alone for busy stakeholders.
Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal
Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.
Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.
Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.