Markdown Report
Create useful Markdown documents with clear structure and practical detail.
Workflow
Identify audience and purpose
- Decide whether the report is for personal tracking, engineering, leadership, research archive, automation output, or public sharing.
Choose the lightest structure
- Use only the headings needed for the job.
- Prefer concise sections over heavy templates.
Write
- Put the answer near the top.
- Use clear headings and short paragraphs.
- Use tables only when they improve comparison or scanning.
- Make action items explicit.
Verify
- Confirm the title matches the purpose.
- Confirm claims are sourced, grounded in files, or clearly labeled as assumptions.
- Confirm action items are concrete.
- Confirm Markdown renders cleanly.
Common Templates
Research Brief
# [Title]
## Summary
## Key Findings
## Evidence
## Recommendations
## Action Items
## Sources
Decision Record
# Decision: [Title]
## Context
## Options Considered
## Decision
## Rationale
## Risks
## Follow-ups
Rules
- Respond in the user's language.
- Do not over-format simple content.
- Do not bury the useful answer below background.
- Do not include unsupported claims.