---
name: finance-wayfinder
description: Map a large, ambiguous financial modeling or finance analysis effort into decision tickets before execution. Use when the user wants to figure out the path for a major model, business case, valuation, investor analysis, pricing strategy, capacity plan, or finance research effort that is too foggy for one session.
---

# Finance Wayfinder

Use this for finance efforts where the destination is real but the route is not yet visible. This adapts wayfinder's map-and-frontier method to finance.

## Workflow

1. Read `../../references/finance-workflow.md`.
2. Name the destination in finance terms:
   - the decision to make
   - the artifact needed
   - the audience
   - the confidence bar
3. Separate current facts from fog:
   - known sources
   - known assumptions
   - sharp questions that can become tickets
   - vague areas that stay in `Not yet specified`
   - out-of-scope work
4. Create a map artifact in markdown when no issue tracker is available.
5. Create ticket-sized questions. Each ticket should fit one agent session and resolve one decision.
6. Use ticket types:
   - `research`: filings, market data, source discovery, accounting policy
   - `prototype`: rough model skeleton, output mock, driver tree, sensitivity table
   - `grilling`: human decision on scope, audience, scenario philosophy, materiality
   - `task`: obtain files, clean exports, permission/access, convert workbook
7. Stop after charting the map unless the user explicitly asks to resolve one ticket.

## Local Markdown Map Shape

```markdown
# Finance Wayfinder: [Destination]

## Destination

## Notes

## Decisions so far

## Open Tickets

### [Ticket title]

Type:
Question:
Blocked by:

## Not yet specified

## Out of scope
```

Refer to tickets by title, not bare IDs.