Planificación de mapas mentales

# Mind Map Planning

## When to use

Turn a topic and supporting evidence into a concise, reviewable hierarchy for a mind map or concept diagram.

## Workflow

1. Confirm the user owns the input or has permission to process it. Collect the source material, audience, output format, and acceptance criteria.
2. Separate observed facts and user-provided constraints from inference. Ask for missing information instead of inventing it.
3. Define the root topic, intended audience, depth, branch direction, and the questions the map must answer before drafting nodes.
4. Use <skill-tag>skill:4b07bbf2-25cd-5e6c-b5fc-d7297b9783e6</skill-tag> when current evidence is needed. Return a plaintext hierarchy with one root, three to five primary branches, and concise leaf labels.

## Output contract

Return the input assumptions, the approved plan, the generated or analyzed result, uncertainty and limitations, and a concise verification checklist. Preserve source links and provider-returned identifiers when available. Stop if the required connected capability is unavailable; do not substitute local scripts, package installation, or embedded credentials.

## Safety and review

Do not upload private or sensitive media without explicit authorization. Do not claim certainty beyond the evidence. Require review before externally visible, paid, destructive, or account-changing actions.

## Source and license

This Aident-native re-authoring is based on [the pinned upstream source](https://github.com/clearsmog/claude-skills/tree/b970f3f778593963d1ea255d2854c7f42b91c832/mindmap), discovered through [ModelScope](https://modelscope.cn/skills/@clearsmog/mindmap), and used under MIT. It preserves the upstream workflow goal while removing local executable, credential, and package assumptions.