Matt Pocock’s skills v1.1 connects planning to implementation. His new Wayfinder skill tackles a problem before the spec: how to make progress when the destination is too uncertain or the work too large for one agent session.

From a fuzzy idea to a map

Wayfinder records a shared map in an issue tracker and divides the open questions into session-sized tickets with blocking relationships. Pocock shows a proposed AI SDK dependency change where some decisions depend on earlier ones. Research tickets let an agent investigate independently; grilling tickets need a person’s decisions; prototype tickets make a rough artifact to react to. Ordinary tasks cover things such as access or configuration.

When the tickets close, the map keeps their findings and links back to the original issues. The completed map can then become a specification. Pocock says this reduces his need to manage a single long session and its limited context. He recommends prototypes especially when a feature’s appearance or behavior is still in question.

A flow from decisions to reviewed code

Pocock describes a sequence: interview the user and record terminology and architectural decisions, create a spec, split it into tickets, and implement tickets in separate sessions. Wayfinder can replace the earlier interview-with-documents stage for larger plans.

The new /implement skill calls for test-driven development at agreed seams where possible, regular type checks and individual tests, a full suite at the end, code review, and a commit to the current branch. His review uses parallel agents to check repository standards and fidelity to the spec. It also names refactoring smells, such as duplicated code and data clumps, for the reviewer to look for. Pocock reports that this improved his own code; the video is a walkthrough, not a controlled evaluation.

Smaller changes and migration

  • /to-prd becomes /to-spec, because the resulting specification can combine technical and product decisions. /to-issues becomes /to-tickets, a name less tied to particular trackers.
  • Grilling instructions emphasize one question at a time and require confirmation before implementing. They distinguish facts an agent can find in the repository from decisions for the user.
  • /research asks a background agent to consult primary sources and save findings according to repository conventions. /prototype supports logic and UI prototypes.
  • The TDD material becomes reference guidance centered on red then green, one slice at a time. Pocock moves refactoring to review so implementation has less to juggle.

Pocock warns that renamed skills may need to be removed and re-added. His video recommends checking the installed skills afterward, especially if they contain local changes.