feat: add native Wayfinder-style task planning - #1
Draft
pruge wants to merge 2 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Firstmate-native planning/decomposition layer inspired by Matt Pocock's Wayfinder, to-spec, and to-tickets skills.
Design
spec.md+ verticaltickets/.implementphase, separate runtime, branch orchestration, and mandatory per-ticket review are intentionally not imported.data/<task-id>/plan/and expose conclusions/rationale rather than hidden chain-of-thought.Current scope
This PR adds the internal skill and documentation. The skill's metadata is designed for Firstmate's normal skill discovery. No existing dispatch, brief, spawn, delivery, or merge machinery has been replaced.
Next integration step
Validate the skill in a real Firstmate session with a representative medium/large request, then decide whether an explicit routing sentence in
AGENTS.mdis necessary after observing the harness's skill-discovery behavior. If needed, add that as a follow-up rather than coupling the first change to a large rewrite of the always-loaded contract.This is intentionally staged so the existing firstmate lifecycle remains unchanged until the planning behavior is proven in practice.