---
name: technical-blog-post-outliner
description: "Structures a technical tutorial or engineering blog post into a detailed outline with headings and bullets, sized to the reader's level. Use when a writer wants to write a tutorial or engineering blog post and needs a detailed outline with sections and bullets first. Do not use for polishing a finished technical draft or writing the full post. Related topics: writing, coding, content creation."
---

# Technical Blog Post Outliner

Structures a technical tutorial or engineering blog post into a detailed outline with headings and bullets, sized to the reader's level.

## When to use

Use this skill when a writer wants to write a tutorial or engineering blog post and needs a detailed outline with sections and bullets first. Do not use it for polishing a finished technical draft or writing the full post.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Restate the main takeaways as what the reader can do after reading.
3. Order the chosen sections so each depends only on earlier ones.
4. Under each heading list the points, code snippets, or examples to cover at the right depth for the skill level.
5. Add the performance and best practices section if requested.
6. Scale the outline to the length and finish with a suggested title and one-sentence hook.

## Inputs

- **Topic or title** (free text, e.g. "How to build a REST API in Go")
- **Target audience skill level** (choose one: Beginner, Intermediate, Advanced, Expert)
- **Main takeaways for the reader** (longer free text)
- **Sections to include** (choose any: Prerequisites, Setup and Installation, Step-by-Step Code, Common Errors, Conclusion)
- **Include a performance and best practices section** (choose one: Yes, No)
- **Desired length of the final post** (choose one: Short (500 words), Medium (1500 words), Long-form Deep Dive (3000+ words))

## Output

A markdown outline with a heading per section and bullets under each, plus a suggested title and one-sentence hook.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Technical Blog Post Outliner

Structure my technical knowledge into an outline for a tutorial or engineering blog post.

- Topic or title: {{Topic or title}}
- Target audience skill level: {{Target audience skill level}}
- Main takeaways for the reader: {{Main takeaways for the reader}}
- Sections to include: {{Sections to include}}
- Include a performance and best practices section: {{Include a performance and best practices section}}
- Desired length of the final post: {{Desired length of the final post}}

Order sections so each depends only on earlier ones. Match depth to skill level: a Beginner needs definitions and every command, while an Expert needs trade-offs and edge cases. Under each heading give bullets of what to cover, including which code snippet or example belongs there. Scale the number of sections and bullets to the length.

Return a detailed outline in markdown with headings and bullet points for each section, ending with a suggested title and a one-sentence hook.

## Pitfalls

- A Beginner outline that skips setup steps the reader needs.
- Ordering sections so code uses concepts explained later.
- An outline too detailed for a short post or too thin for a deep dive.
