Wayfinder
Plans work too big for one session as a shared map of decision tickets, resolved one at a time until the way is clear
- What
- Plans work too big for one session as a shared map of decision tickets, resolved one at a time until the way is clear
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a planning skill for efforts too big and foggy for one agent session. It charts the way as a shared map on your issue tracker: one map issue (labelled wayfinder:map) holding the destination, notes, decisions-so-far and out-of-scope, with child issues as decision tickets — questions whose resolution is a decision, not slices of build to execute. Tickets come in four types (research, prototype, grilling, task) and are claimed by assignee so parallel sessions don't collide; the frontier — open, unblocked, unclaimed tickets — is found by query, and what can't be specified yet lives deliberately in a "fog of war" section until resolutions graduate it into fresh tickets. Wayfinding is planning, not doing: the map is done when nothing is left to decide. Human-in-the-loop tickets are never resolved by the agent alone, and tickets are always referred to by name, never by bare id. By @mattpocock, listed here with credit to its creator. Honest caveats: it creates issues and wires blocking edges on your tracker — it needs your tracker configuration (docs/agents/issue-tracker.md) or it falls back to a local-markdown tracker; never resolves more than one ticket per session by design, so big efforts take many sessions. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "Wayfinder" for me. Plans work too big for one session as a shared map of decision tickets, resolved one at a time until the way is clear Repository: https://github.com/mattpocock/skills/blob/main/skills/engineering/wayfinder/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-wayfinder". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.