Send the plan.
The build follows.

PathfinderNew in 2.0

For an idea that arrives too foggy to plan. It charts the idea as a map of decision questions and clears them one at a time until nothing is left to decide.

it never answers its own questions — that's the point

• One decision per file, cleared one at a time
• Ask for a brief — plain-English minutes, any time
• Research questions fan out to parallel agents
• Clears at ≥18/25 on four confidence dimensions
• Hands a hot plan draft to Step 1

Plan

A real back-and-forth about what gets built. Requirements pulled apart, your codebase actually read, the stack confirmed rather than assumed.

• Functional and non-functional requirements
• Integration points read from real source
• Tech stack confirmed by explicit approval
• Will not finalize below 90% confidence

Document

The plan stops being a conversation and becomes files — an overview plus one self-contained phase document per phase, cut into one-story-point tasks.

• overview.md and Phase 1…N.md land in your repo
• One-point tasks with real checkboxes
• Parallel groups marked for concurrent agents
• Each phase readable with no prior context

Implement

Build to the drawing, one phase per conversation. Planning context bleeding into implementation is where most agent drift starts.

reply “approved” — nothing advances on a guess

• Fresh conversation for every phase
• Specs followed exactly as documented
• Self-review against the spec before close
• [/] claims prevent parallel-agent collisions

ReviewSecond opinion

An independent senior engineer with fresh eyes and no attachment to the code that just shipped. It reads every changed file completely and reports only what it can prove — file, line, and a concrete fix.

• Scope adapts: files, branch diff, or subsystem
• All 11 dimensions reported, clean ones justified
• Ranked Critical / Warning / Suggestion
• Read-only until you reply H, A, or S 1,3,5

Finalize

Close it out. Every task audited against the spec it came from, a summary of what was built, docs checked for drift, and the folder filed away.

• Audit for tasks quietly left open
• Summary of what was built and changed
• README and other docs reconciled
• Specs archived to specs--completed/