@mattpocockuk: One clarification for folks using /wayfinder: The flow for big work should be: /wayfinder -> /to-spec -> /to-tickets ->…

X AI KOLs Following Tools

Summary

Matt Pocock clarifies the intended workflow for /wayfinder, emphasizing the flow from /wayfinder to /to-spec to /to-tickets to /implement for coding projects, and notes that v1.2 is in development.

One clarification for folks using /wayfinder: The flow for big work should be: /wayfinder -> /to-spec -> /to-tickets -> /implement Once the /wayfinder map is complete, you turn it into a spec. Some folks are using /wayfinder as the ENTIRE flow - from grilling to prototyping to shipped work It certainly can be used that way - I've been doing that for non-coding stuff like course creation. But for coding I much prefer creating a spec and handing off implementation to an AFK agent. Means I can focus on other things for a bit while it churns away. I'll be putting all of this in an upcoming tutorial. Thanks for all the great feedback on v1.1. v1.2 is in the works and looking good.
Original Article
View Cached Full Text

Cached at: 07/11/26, 09:25 AM

One clarification for folks using /wayfinder:

The flow for big work should be:

/wayfinder -> /to-spec -> /to-tickets -> /implement

Once the /wayfinder map is complete, you turn it into a spec.

Some folks are using /wayfinder as the ENTIRE flow - from grilling to prototyping to shipped work

It certainly can be used that way - I’ve been doing that for non-coding stuff like course creation.

But for coding I much prefer creating a spec and handing off implementation to an AFK agent. Means I can focus on other things for a bit while it churns away.

I’ll be putting all of this in an upcoming tutorial. Thanks for all the great feedback on v1.1. v1.2 is in the works and looking good.

Similar Articles