allank

Builds a self-contained interactive HTML visualisation that makes a process, algorithm, decision logic, or system experientially understandable.

Router for the pm-craft plugin — matches your need to the right skill and tells you what to type.

Write a per-topic handoff file and log it in a single index at the end of a working session, so any topic can be resumed later in a fresh session. Use when the user wants to wrap up or park a session ("handoff", "wrap up", "park this"), or to resume or pick up a previous topic. Also suggest it proactively when a substantive session is clearly winding down.

Simulates a Visionary-vs-Skeptic debate over a product idea, then synthesises a path forward.

Use the Obsidian CLI to interact with the vault natively—search, read, create, manage tasks, properties, and daily notes. Prefer CLI over raw file I/O for vault-aware operations.

Use when stress-testing a product idea before committing — interviews the user on six PM lenses and produces a conviction brief alongside the session.

Analyses a problem through mental-model lenses — 11 personas and 20 frameworks, four modes (Tuning, Solo, Counterpoint, Harmony), Simple and Expert tracks.

A strategic thinking partner that broadens perspective using systems thinking frameworks — Cynefin, Three Horizons, Wardley Mapping, Idealised Design, Intuition Pumps. Use when the user wants to 'think bigger' or 'widen the lens', asks for a sanity check on a strategy, feels stuck fire-fighting or in a creative rut, or names one of the frameworks.

Use when stress-testing a product idea before committing — interviews the user on six PM lenses and produces a conviction brief alongside the session.

Builds a self-contained interactive HTML visualisation that makes a process, algorithm, decision logic, or system visually and experientially understandable. Primary input is a linear walkthrough, but works directly from code, documents, or concept descriptions too — and can invoke the linear-walkthrough skill as an intermediate step if the source material lacks sufficient clarity or structure. Use when the user wants to "see how this works", wants an interactive version of a walkthrough, wants to explain a process visually to an audience, or asks to "visualise", "animate", or "build an interactive explanation" of anything. Richer and more interactive is always preferred, as long as it makes the logic clearer rather than decorating it.

Generates a linear, narrative walkthrough of source material — code, documents, architecture diagrams, meeting notes, Jira tickets, or any combination. Produces a step-by-step guide that explains logic, purpose, and connections between components in a readable sequence. Use when the user wants to understand how something works, wants to explain a system to others, asks to "walk through" or "explain" code or docs, or needs to document a system's logic for learning or onboarding. Also trigger when the user provides files or code and asks "how does this work?" or "take me through this."

Converts Markdown files to Google Docs-friendly DOCX format using Pandoc (via a helper script).

Use the Obsidian CLI to interact with the vault natively—search, read, create, manage tasks, properties, daily notes, and more. Prefer CLI over raw file I/O for vault-aware operations.