Your agent's planning skills, served.
Composed for your harness. Substituted for your issue tracker. Extended with the skills your team registered.
Install once, for every repo on the machine. A Homebrew tap ships the same build.
Writes one stub skill per agent harness, and records your issue tracker.
Your agent runs this. It prints the wayfinder skill, and the rest follows.
Copies drift
Every repo holds its own copy of every skill, so an upstream improvement reaches no repo without a manual sweep. The content ships inside the CLI instead. Upgrade the CLI and every skill upgrades with it.
Skills hardcode each other
A skill that says "run /grilling" works only while you keep that skill, under that name, in that harness. The render composes instead. A dependency every path needs is inlined; a dependency only some paths need becomes a command plus the condition that fires it.
Skills assume one tracker
GitHub prose in a Jira repo is worse than no prose. Name your tracker and the render appends the operations for it. A repo with no tracker set gets a block that asks the human — never a silent guess.
Your own skills join the plan
Register a harness skill with one sentence that says when it applies. The charting agent reads that sentence and writes the skill into every ticket it covers — your pre-mortem, your design loop, your review checklist.
One setup for the whole team
Project scope is a committed file. Every contributor and every agent renders the same skills, the same tracker, and the same registrations, with nothing to configure per person.
Adoption is one command
Run wayfinder init once per repo. There is nothing to copy, nothing to keep in step, and nothing for a new joiner to install by hand.
New to wayfinding? This site documents the CLI, not the method — start at aihero.dev/skills-wayfinder.