pathfinder

What problem does it solve? Large features and systems are too big to design in one session, and design work drifts into implementation detail before the overall shape is agreed. Pathfinder enforces a staged descent — intent, parts, seams, interiors — so architecture decisions happen at the right level of detail and are recorded on the issue tracker. ## Core Features & Use Cases - Altitude-gated planning: Works at exactly one altitude per session (A0 Intent through A4 Ready), parking any lower-level detail instead of answering it prematurely. - Tracker-native state: Represents the plan as a pathfinder:path GitHub issue with child leg issues, labels, assignees, and native blocking dependencies, so any session can resume without local state. - Typed legs with HITL/AFK modes: Each leg is a survey, research, prototype, or task with dispatch metadata, claim comments, and resolution records. - Use Case: You need to design a new dispatch system spanning multiple services. Pathfinder charts a path issue, runs an A0 intent survey with the human, creates A1 parts legs, and hands off a frontier of ready, scoped tickets to implementers — without writing any application code. ## Quick Start Ask the agent to use pathfinder to chart a path for your big feature idea, starting with an A0 intent survey and creating the path issue on the tracker.