Demo Document Generator

A skill for generating clean, professional documents with consistent structure.

When to apply this skill

Use this skill for:

• - Technical specifications and feature docs
• Project reports and status updates
• API or module documentation
• Meeting minutes and decision logs
• README files and onboarding guides

Document Generation Workflow

1. 1. Understand the document type — identify what kind of document is needed and who will read it
2. Gather key information — ask only the essential questions (purpose, audience, main content points); don't over-ask
3. Choose the right template — pick from the templates below based on type
4. Write the draft — fill in the template with real content, not placeholder text
5. Review for clarity — ensure each section adds value; cut anything redundant

Templates

Technical Specification

CODEBLOCK0

Project Status Report

CODEBLOCK1

Meeting Minutes

CODEBLOCK2

README / Onboarding Guide

CODEBLOCK3bash

Installation and first run

Writing Principles

• - Lead with the "why" — readers should immediately understand the purpose
• Use concrete examples — show real values, real code, real names; avoid foo/bar placeholders
• Keep sections lean — one section = one idea; if a section feels thin, fold it into another
• Tables over lists for structured comparisons; bullet lists for independent items
• Active voice — "The API returns X" not "X is returned by the API"

Output Format

Always produce the document as a markdown code block so it's easy to copy. If the user seems to want a file saved to disk, write it as a .md file in the current directory and tell them where it is.