---
name: mind-map-outline-helper
description: "Structures a central topic into non-overlapping branches for a stated audience and constraint, as a clean list that pastes straight into mind-mapping software. Use when a mind map skeleton is needed for one topic, with non-overlapping branches worded for a particular audience. Do not use for expanding a short idea with examples or sorting a messy brainstorm. Related topics: productivity, work, Mind Map."
---

# Mind Map Outline Helper

Structures a central topic into non-overlapping branches for a stated audience and constraint, as a clean list that pastes straight into mind-mapping software.

## When to use

Use this skill when a mind map skeleton is needed for one topic, with non-overlapping branches worded for a particular audience. Do not use it for expanding a short idea with examples or sorting a messy brainstorm.

## 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 the central topic as the header and set the chosen branches under it.
3. Test each branch pair for overlap and move shared items to one home.
4. Write sub-branches to the chosen depth that reflect the key constraint.
5. Word every node for the audience in the chosen tone.
6. Output only the indented list.

## Inputs

- **Central topic** (free text, e.g. "The main subject")
- **Primary branches** (choose any: Strategy, Operations, Finance, Risk, Team, Technology, Marketing)
- **Depth level** (choose one: 2 levels, 3 levels, 4 levels)
- **Tone** (choose one: Formal, Casual)
- **Audience** (free text, e.g. "Who will read this map")
- **Key constraint** (longer free text)

## Output

A Markdown list headed by the central topic, with two-space indentation per level and no explanatory text.

## Prompt template

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

### Mind Map Outline Helper

Build a mind map skeleton for one central topic, tuned to its reader.

- Central topic: {{Central topic}}
- Primary branches: {{Primary branches}}
- Depth level: {{Depth level}}
- Tone: {{Tone}}
- Audience: {{Audience}}
- Key constraint: {{Key constraint}}

Check each pair of branches for overlap and move any shared item to the branch where it belongs most. Word the nodes for the stated audience in the chosen tone and shape the sub-branches around the constraint, so the constraint appears in the structure and not as a footnote. Use specific structural elements, such as named decisions or deliverables, rather than generic advice.

Return a Markdown list with the central topic as the main header. Indent each sub-level by two spaces. Use only standard list syntax and add no explanatory text.

## Pitfalls

- Overlapping branches such as Finance and Risk both holding budget items.
- Generic nodes like improve efficiency that say nothing about the topic.
- Adding commentary when the output must paste cleanly into mapping software.
