What problem does it solve? Long-running projects with unresolved dependent decisions lose track of open questions across sessions, causing premature coding, duplicated specifications, and conflicting plans. This Skill maintains a single-writer decision map that tracks open questions, dependencies, and staleness until the work is ready for specification and planning. ## Core Features & Use Cases - Decision Frontier Tracking: Records open items as precise questions with IDs, dependencies, states, and owners, keeping implementation tasks and estimates out of the map. - Single-Writer Map Ownership: Enforces one lead controller as sole writer of the map at docs/superpowers/plans/wayfinding/, with other sessions returning read-only findings. - Closure and Handoff Gates: Closes only when no stale items remain and approved behavior has been promoted through skill-spec-drafting, then hands off to skill-writing-plans for implementation sequencing. - Use Case: A team starting a multi-week migration with a known goal but unresolved design dependencies uses wayfinding to map decision questions across sessions, refusing premature code requests until the frontier is settled. ## Quick Start Invoke wayfinding to open a decision map for my multi-session migration project and track the unresolved dependent questions before any specification or coding begins.
