research-wayfinderlisted

# Research Wayfinder ## Heritage and scope Adapted from Matt Pocock's **wayfinder** (MIT, [mattpocock/skills](https://github.com/mattpocock/skills); see [`RECOMMENDED.md`](../../RECOMMENDED.md)). His insight carries over whole: give up on the session as the unit of work. The map lives in the repository, any future session picks it up, and the context window stops being the source of truth. What changes here is the destination and the ticket taxonomy. Wayfinder charts a route to a shippable spec. Research-wayfinder charts a route to a **defensible, pre-registerable research design**, and its decisions are the ones experimental methodology actually forces: estimand before estimator, theory before if-then, power before fielding. Use it early. Vagueness is not a reason to wait; it is what the map eats. The map ends where `pre-registration-writing` begins — this skill does not run analyses or draft the paper. ## The map `planning/map.md` in the project repo (fits the `research-repo` scaffold; GitHub Issues works when the project is hosted on GitHub, but local markdown is the default and needs nothing). The map is an **index, not a store**: ```markdown # Map — <project name> Destination — <what a finished design looks like — the study you could pre-register tomorrow> Notes — <domain context, standing preferences, constraints — budget, panel, timeline> ## Decisions so far - [x] tickets/001-estimand.md — <one-line gist of the resolution> ## Frontier (open, unblocked, unclaime