/wayfinder and /to-tickets tickets in the same folder?

[T3rm1]

I started with /wayfinder. This created tickets in .scratch/<topic>/issues/.
After that I used /to-spec and then /to-tickets. The latter put the tickets in the same folder. Is this correct? I have the feeling, that when implementing one ticket, the agents get confused because the also read the wayfinder tickets.

[RafaelHDSV]

The shared folder is expected for local-markdown mode. It is also the wrong input for /implement.

Local tickets from both skills land under .scratch/<topic>/issues/:

• /wayfinder writes decision tickets (a question whose resolution is a decision, labelled wayfinder:…). The map is planning only. Docs: “Wayfinder's tickets are decision tickets… What is left is a map full of linked decisions, which is not a build plan.”
• /to-tickets writes tracer-bullet implementation tickets (vertical slices with blocking edges, ready-for-agent). Same directory layout, different kind of issue.

So /to-tickets putting files next to the wayfinder tickets is correct for the local tracker. The confusion you are seeing is also described in the wayfinder docs: agents that /implement a wayfinder ticket start building from a question, or they load every issues/*.md in the folder and mix planning notes into the coding context.

Intended pipeline (from the wayfinder FAQ):

1. Finish the wayfinder map (all decision tickets closed).
2. /to-spec #<map> — collapse the linked decisions into one spec.
3. /to-tickets — slice that spec, not the wayfinder tickets.
4. /implement only the to-tickets files.

Do not point implement at the wayfinder issues. If you already mixed them:

• Use a new topic name for the build (.scratch/<build-topic>/issues/) so implement never lists the decision tickets.
• Or move/archive the wayfinder:* files out of that folder before implementing.
• On GitHub/Linear this is cleaner: wayfinder issues stay on the map with wayfinder: labels and never get ready-for-agent.

If this matches what you hit, please mark the answer as accepted.

[T3rm1]

I did it like you described in steps 1 to 4. But when I used /implement on the to-tickets, the agent got confused by the decision tickets. I didn't find any documentation recommending to manually separate the decision tickets from the implementation tickets. I think this is missing and it's important to mention somehwere. Ideally the to-tickets skill knows about this issues and choses a separate topic name.

Another problem I just noticed is that during wayfinding, the agent created an api-contract.md on the same level as the issues folder. This file references the wayfinder tickets. So if I followed you suggestion and archive the wayfinder tickets, I'd have to also archive the api contract file. However, I think this one is crititcal for the actual implementation work.