Wayfind a large effort

Use this skill when the destination matters but the route cannot yet fit in one working session. If the work is already well scoped, recommend a lighter plan or implementation workflow.

1. Name the destination and its scope with the user.
2. Inspect the configured tracker and existing decisions. Choose a map representation that collaborators and agents can query reliably.
3. Create a low-resolution map: settled decisions, sharply stated open questions, dependencies, unresolved fog, and explicit out-of-scope work. Avoid inventing detailed tickets for questions that are not yet clear.
4. Advance independent questions concurrently when ownership and writes do not conflict. Keep human judgment in the loop for product or preference decisions; use research or prototypes when evidence is missing.
5. After resolving a question, record the decision once, update affected dependencies and fog, and expose the next useful frontier.
6. Hand off when the route is clear enough for specification or execution. Wayfinding may produce work only when doing so is necessary to resolve a decision.

Read references/map-model.md when creating or repairing a map. Read references/workflows.md for charting, advancing, concurrency, and handoff choices.