---
name: mind-map-outline-manager
description: "Organises your own list of subtopics into a mind-map outline, as a bullet list, hierarchical tree or JSON, with optional real-world examples. Use when a list of subtopics already exists and needs building into a mind-map outline, possibly as JSON for a tool. Do not use for turning an unstructured brainstorm into a hierarchy or planning a project with dependencies. Related topics: productivity, work, Mind Map."
---

# Mind Map Outline Manager

Organises your own list of subtopics into a mind-map outline, as a bullet list, hierarchical tree or JSON, with optional real-world examples.

## When to use

Use this skill when a list of subtopics already exists and needs building into a mind-map outline, possibly as JSON for a tool. Do not use it for turning an unstructured brainstorm into a hierarchy or planning a project with dependencies.

## 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. Place every listed subtopic at the second level without changing its wording.
3. Add child nodes down to the chosen depth that are specific to each parent.
4. Note any listed subtopic that really belongs under another, and leave it where listed.
5. Add one example under each subtopic when examples are on.
6. Render in the chosen style and check the JSON is valid when selected.

## Inputs

- **Core topic** (free text, e.g. "Main idea or project name")
- **Subtopics** (longer free text)
- **Depth** (number from 1 to 5)
- **Include real-world examples** (choose one: Yes, No)
- **Output style** (choose one: Bullet List, Hierarchical Tree, JSON)

## Output

The outline in the chosen style: markdown headings or lists, or a valid nested JSON object with name and children keys.

## Prompt template

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

### Mind Map Outline Manager

Build an outline around the subtopics I have listed.

- Core topic: {{Core topic}}
- Subtopics: {{Subtopics}}
- Depth: {{Depth}}
- Include real-world examples: {{Include real-world examples}}
- Output style: {{Output style}}

Use my subtopics as the second level and do not drop or rename any of them. Add deeper levels under each only as far as the depth allows, with every child a specific part of its parent. If a subtopic is clearly a child of another, point it out and keep it where listed. When examples are on, add one example sentence under each subtopic. For JSON, use an object with keys name and children, nested to the chosen depth, and a key example when examples are on.

Return the outline in the chosen style: markdown headings and lists for the first two, and valid JSON for the third.

## Pitfalls

- Quietly merging or renaming subtopics the user supplied.
- Invalid JSON, such as trailing commas, which breaks import.
- Examples that are generic and could apply to any topic.
