Build a map with your AI agent

The included skill teaches an AI agent the exact markdown md2hd can draw. Use it when the source material already exists, or when you can describe the map you need.

Add the skill

Get the writing-md2hd-maps skill from the repository. Add that folder to the skills directory used by your agent.

Ask the agent to confirm that it can read the skill before giving it the map task. The agent needs the complete SKILL.md, not a summary of it.

Describe the result

Tell the agent where the notes are, which kinds of things matter, and which questions the map should answer.

Use the writing-md2hd-maps skill.

Read the markdown in ./planning. Build one md2hd map of the Q3 launch.
Include projects, people, systems, dates, and blockers. Name relationships so I
can see who owns each project, what each project depends on, and what blocks it.
Give important launch work more weight. Return the markdown file and verify the
connections before you finish.

You can also start without source files:

Use the writing-md2hd-maps skill. Create a small service map for this flow:
the Checkout API publishes to the Payments Queue, the Reconciler drains that
queue, and both write to the Ledger. The Platform Team operates the API.

The agent should return ordinary .md files. Keep them with the rest of your notes or in a folder of their own.

Open the markdown

Open md2hd, choose Import markdown files or Import markdown folder, and select what the agent wrote. You can also paste a complete map into the import dialog.

Before opening it, md2hd reports the number of cards and connections it found. After opening it, check three things:

1. Every expected card appears.
2. Every connection has a useful label.
3. Arrows point in the intended direction.

Ask for corrections

A gray dashed card means the agent referenced an ID it never defined. A backwards arrow usually means a passive label ending in _by or an incorrect inverse: pair. An unlabeled gray line came from a bare wikilink.

Send the markdown back with a precise correction:

Use the writing-md2hd-maps skill to correct this map.

- Define or remove every unresolved card.
- Replace bare mentions with named relationships where the connection matters.
- Read back every connection after direction normalization.
- Keep the existing IDs unless an ID is the error.

Then import the corrected file again. The markdown remains yours to edit, version, and reuse.

Next

Read the manual quickstart to understand the file the agent produced, or keep the markdown reference open while you review it.