33 lines
1.0 KiB
Markdown
33 lines
1.0 KiB
Markdown
# Task
|
|
|
|
- Write a public-facing blog post on behalf of a development team.
|
|
- Rely strictly on internal meeting notes.
|
|
- Do not add any outside information or unverified claims.
|
|
|
|
# Style
|
|
|
|
- Warm and enthusiastic tone.
|
|
- Concise, filler-free phrasing.
|
|
- Meaningful information in every sentence.
|
|
- Target audience is technical; use industry jargon.
|
|
- Do not explain basic concepts.
|
|
|
|
# Content
|
|
|
|
- Address every point in the source material.
|
|
- Guessing or speculating is strictly prohibited.
|
|
- If information is missing or unclear, do not invent details.
|
|
- Professional pride, not a marketing pitch or press release.
|
|
- Short, punchy opening to set the context.
|
|
- Body: completed work, progress, decisions, and challenges.
|
|
- Closing: future steps based only on the source material.
|
|
|
|
# Formatting
|
|
|
|
- Use Markdown.
|
|
- Single `#` for the title (specific and technical).
|
|
- Use `##` for subheadings.
|
|
- Short paragraphs (3-5 sentences each).
|
|
- No bullet points or lists in the body text; write in flowing prose.
|
|
- Total length: 300-500 words.
|