Help us improve
Share bugs, ideas, or general feedback.
Retrieves DoView Planning handbook diagrams as Mermaid blocks (primary) or PNG fallback URLs to accompany outcomes-theory answers.
npx claudepluginhub cgbarlow/skills --plugin doview-image-retrieverHow this skill is triggered — by the user, by Claude, or both
Slash command
/doview-image-retriever:doview-image-retrieverThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> Faithful adaptation of *Prompt B — Outcomes Theory Book Image Retriever Prompt (v1.1.9)*
Generates professional diagrams (flowcharts, architecture diagrams, comparisons, mind maps, timelines) as draw.io XML files from concepts or documents.
Creates technical and product diagrams (architecture, flowchart, sequence, etc.) as standalone HTML files with inline SVG. Includes style guide setup and 14 diagram types.
Generates Excalidraw diagram JSON files that argue visually, not just display information. Use for workflows, architectures, or concepts.
Share bugs, ideas, or general feedback.
Faithful adaptation of Prompt B — Outcomes Theory Book Image Retriever Prompt (v1.1.9) from https://www.doviewplanning.org/bookai. Source content © Dr Paul W Duignan and DoViewPlanning.Org. Extended to retrieve Mermaid blocks as the primary representation (the source diagrams are available as Mermaid in the doview-book repo), with the upstream PNG/image-file rules preserved as a fallback.
Prompt B was originally written to retrieve and embed PNG images from doviewplanning.org pages. In this skill's context, the same diagrams are available as Mermaid code blocks inside chapter tool.md files in https://github.com/cgbarlow/doview-book under docs/md/Part X - …/Xnn - …/. When the cited chapter has a Mermaid block, retrieve and reproduce the Mermaid block as the primary visual. When the chapter's tool.md notes "does not translate cleanly to Mermaid" (a small number of poster-style diagrams), fall back to the upstream PNG/image-file URL behaviour against the doviewplanning.org source page.
The Mermaid-first additions appear below as clearly-delimited subsections labelled MERMAID-FIRST EXTENSION. Everything outside those subsections is byte-identical to the upstream Prompt B v1.1.9.
Prompt B: Outcomes Theory Book Image Retriever Prompt (for use directly after Prompt A response has been generated) Prompt B: Outcomes Theory Book Image Retriever Prompt Version: 1.1.9 Use this page as the source page for retrieving relevant images from Dr Paul Duignan’s outcomes theory handbook and its linked tool pages: https://doviewplanning.org/bookai Use this prompt after Prompt A: Outcomes Theory Text Response Prompt has produced a response. Look at the response immediately above and identify the full visible plain-text URLs in it. First look for the heading: Image-retrieval seed list for Prompt B Use the URLs under that heading as the primary pages to inspect for relevant images. If that heading is absent, use the full visible plain-text URLs in the response above. Check only those URLs, and only the permitted outcomes theory handbook and tool pages from Dr Paul Duignan’s DoView Planning and Outcomes Theory Handbook: https://doviewplanning.org/book and the individual tool pages linked from that handbook, running from: https://doviewplanning.org/a1doviewtool through to: https://doviewplanning.org/j7doviewtool Do not use any other part of the DoView website. Do not use the rest of the internet. Do not use general knowledge. TASK Identify whether any directly relevant DoView Board, diagram, figure, image, or visual model appears on the permitted pages and is relevant to the answer immediately above. The purpose of this prompt is to retrieve relevant source images faithfully. It is not to write a new outcomes theory answer. IMAGE DISPLAY LIMITATION WARNING Begin the response with this note: This image-retrieval response attempts to display the most relevant original images from the permitted handbook and tool pages. Image display depends on the AI system’s technical ability to embed images from source URLs. Some relevant images may appear directly in the chat, while others may only be available as full visible plain-text image URLs. IMAGE PRIORITISATION RULE If many relevant images are found, do not try to include every possible image. Prioritise the most important images for understanding the previous outcomes theory answer. Display or embed as many directly relevant original images as the AI system can reliably include, prioritising:
For each tool URL in the seed list, before falling back to PNG retrieval, check whether the corresponding chapter tool.md in https://github.com/cgbarlow/doview-book/tree/main/docs/md contains a Mermaid code block under a ## Diagram heading. The mapping is by tool code:
https://doviewplanning.org/b16doviewtool → look for the chapter folder whose code is B16 under docs/md/Part B - …/B16 - …/b16tool.md.https://doviewplanning.org/g02adoviewtool → look for docs/md/Part G - …/G02A - …/g02atool.md.<letter><digits><optional-subletter> from the URL maps to a chapter code zero-padded to two digits (e.g. b1 → B01, g25 → G25, g2a → G02A).If the chapter tool.md contains a Mermaid block, reproduce the block faithfully in the response inside a fenced ```mermaid code block. This is the primary representation. The image-file URL (and the markdown image embed line) for the same tool may still be included for AI systems that can render the PNG, but the Mermaid block must be present first.
If the chapter tool.md does not contain a Mermaid block (it carries the note "This page contains a visual that does not translate cleanly to Mermaid; described above."), fall back to the upstream PNG/image-file URL behaviour as written elsewhere in this prompt.
IMAGE FAITHFULNESS RULES If a directly relevant image is found, reproduce it faithfully only by displaying, embedding, or copying the original image from the permitted source. Do not redraw it from memory. Do not simplify it. Do not improve it. Do not create a new substitute image. Do not invent missing labels, arrows, boxes, colours, grouping, or layout. Do not create a new diagram inspired by the source. Do not use an image from outside the permitted handbook or tool pages. If an image-file URL is available, do not state that the image cannot be reproduced unless the system has actually failed to display or embed it. If the original image cannot be faithfully displayed or embedded, state exactly: The relevant image was identified, but this AI system cannot faithfully display or embed the original image here. Then provide:
The above IMAGE FAITHFULNESS RULES apply equally to Mermaid blocks retrieved from docs/md/.../*tool.md:
tool.md.flowchart LR to flowchart TD (or vice versa) to fit chat width — copy the orientation as written.tool.md has explanatory prose under the ## Diagram heading (e.g. NOW / FUTURE annotations), include that prose verbatim immediately after the Mermaid block.OUTPUT FORMAT Begin with this heading: Relevant images from the DoView Planning and Outcomes Theory Handbook, Duignan, P. (2025), https://doviewplanning.org/book Then include the required image display limitation warning. Then, for each relevant image, provide:
When a Mermaid block is being retrieved (the primary path for chapters that have one), the per-image block extends to:
tool.md in https://github.com/cgbarlow/doview-book/tree/main/docs/md/...]<verbatim Mermaid block from the chapter tool.md>
If no directly relevant image is found in the permitted handbook or tool pages, state exactly:
No directly relevant image was identified in the permitted handbook or tool pages.
RAW VISIBLE URL RULE — COPY-SAFE URLS FOR HUMANS
Every page URL and every image-file URL must be written as raw, visible, copy-safe plain text beginning with https://
The purpose of this rule is that a human must be able to copy the response into an email, document, report, or plain-text system and still see every URL.
Do not hide page URLs behind words.
Do not use reference-style links such as “[1]”.
Do not use footnotes.
Do not use source icons.
Do not use citation markers.
Do not use embedded hyperlinks for page URLs.
Do not write “see above”.
Do not write “see links above”.
Do not use shortened URLs.
Exception: markdown image syntax is required only for displaying the original image, and only after the image-file URL has already been written out in full visible plain text.
Correct image format:
Page URL:
https://doviewplanning.org/b16doviewtool
Image file URL:
https://images.squarespace-cdn.com/example/b16tool.png
Original image:
Incorrect image formats:
Page URL: Tool B16
Image: click here
Image file URL hidden behind linked text
See image above
See links above
Only use page URLs from:
https://doviewplanning.org/book
and the linked tool pages from:
https://doviewplanning.org/a1doviewtool
through to:
https://doviewplanning.org/j7doviewtool
Image-file URLs may come from the image files embedded on those permitted handbook or tool pages.
Do not use
https://doviewplanning.org/bookai
as the human-facing handbook reference. The human-facing handbook reference must use:
https://doviewplanning.org/book
REFERENCE
End with this full reference, with the URL written as raw visible plain text:
Duignan, P. (2025). DoView Planning and Outcomes Theory Handbook: 100+ Innovative, Integrated Tools for Solving Key Issues in Planning, Implementation, Contracting, Measurement, Evaluation and Reporting (for Humans and AI Agents).
DoViewPlanning.Org
.
https://doviewplanning.org/book
FINAL COMPLIANCE CHECK BEFORE ANSWERING
Before giving the image response, check and correct the response so that:
Additional checks (this skill only):
tool.md containing a Mermaid block, a verbatim Mermaid block is included in the response before any image-file URL for the same tool.tool.md. Node labels, orientation, and surrounding prose are not paraphrased, prettified, or reordered.tool.md carries the "does not translate cleanly to Mermaid" note, the response falls back to the upstream PNG/image-file behaviour — no synthetic Mermaid block is invented.