# Chart Complex Work Across Agent Sessions

Large efforts lose context when they exceed one agent session. Wayfinder organizes decisions as a shared issue map that agents resolve incrementally.

## Install

```bash
npx skillstore add mattpocock/wayfinder
```

## Metadata

- Status: approved
- Slug: mattpocock-wayfinder
- Skillstore revision: r2
- Version status: missing
- Tree hash: 24c8a58c704b4352fd00079d6110cb0d5fdb6ec1edf1829db3215af92eceb74b
- Author: mattpocock
- GitHub username: mattpocock
- License: MIT
- Repository: https://github.com/mattpocock/skills/tree/main/skills/in-progress/wayfinder/
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/mattpocock-wayfinder
- Manifest: https://skillstore.pages.dev/api/skills/mattpocock-wayfinder/manifest

## Capabilities

- Defines a clear destination and scope for a large, uncertain effort.
- Creates a canonical issue map with child investigation and decision tickets.
- Classifies tickets as research, prototype, grilling, or task work.
- Models dependencies and identifies unblocked, unclaimed frontier tickets.
- Records completed decisions as concise links while preserving detailed ticket context.
- Coordinates parallel sessions through tracker assignments and one-ticket session limits.

## Use Cases

- Plan a Platform Migration: Map architecture decisions, research dependencies, and unresolved risks before implementation begins.
- Coordinate Product Discovery: Organize prototypes, stakeholder questions, and scope decisions across several collaborative sessions.
- Structure a Research Program: Track independent investigations, dependencies, and conclusions without loading every detail into each session.

## Prompt Templates

### Chart a New Map

```
Use Wayfinder to chart this effort: [idea]. Help me define the destination, scope, first frontier, and remaining uncertainty.
```

### Continue an Existing Map

```
Continue Wayfinder map [issue URL or number]. Select the first unclaimed frontier ticket, claim it, and resolve only that ticket.
```

### Resolve a Specific Decision

```
Open Wayfinder map [map reference] and resolve ticket [ticket name]. Consult related decisions only when needed, then update the map.
```

### Reconcile a Changed Route

```
Review Wayfinder map [map reference] after [new decision]. Update dependencies, graduate newly clear questions, and remove invalidated or out-of-scope tickets.
```

## Limitations

- Requires an issue tracker or a local Markdown tracker with documented operations.
- Plans decisions by default and does not deliver the final implementation.
- Relies on companion grilling and domain-modeling skills for guided discovery.
- Handles only one ticket per session, so small efforts may not benefit.

## Best Practices

- Define a measurable destination before creating tickets.
- Keep each ticket focused on one decision that fits one agent session.
- Use tracker assignments and native dependencies to coordinate concurrent sessions.

## Anti Patterns

- Do not use Wayfinder when the complete effort fits one session.
- Do not duplicate full ticket answers inside the map.
- Do not resolve multiple tickets or begin final implementation during one planning session.

## Security Audit

- Audited at: 2026-07-23T17:07:01.036\+00:00
- Summary: All 13 static detections are false positives caused by Markdown backticks, fenced examples, and prose about issue identifiers. The workflow still presents moderate operational risks because it permits consequential tracker changes and may record sensitive operational metadata.

## Stats

- Views: 0
- Downloads: 9
- Favorites: 0
- Popularity score: 0