wayfinder-team

Wayfinder team

For a map.md and its same-directory issues/ child issues, perform concurrent exploration orchestration; the manifest's input.kind: map-issues。map.md is read-only, and additions to the map are made in the form of new issue files; the map itself is not an execution unit, each child issue is. Issues that require code implementation or configuration changes go through the blocked flow (see step 4). This skill has no overlap with PRD/spec implementation tickets or direct-task.

Prerequisite: the target project uses .scratch/<effort>/ to store map.md and same-directory issues/；/wayfinder is provided by mattpocock/skills and must be installed in advance.

Common mechanisms—manifest, frontier scheduling, context hygiene, terminal-state events, independent verification, fail-closed—have their sole source in references/agent-team-protocol.md; this skill only defines input boundaries and steps. The team uses native TeamCreate to create a AgentTeam: the main Agent is the sole coordinator, dispatcher, unlocker, and independent verifier; members share the team context, and unlocking successors is always performed by the main Agent.

Steps

1. Input assessment: read map.md and, under the same-directory issues/ , each child issue's original text,Type:、Status:、Blocked by:, verification/exploration commands, and evidence paths. Check that issue IDs are unique, dependencies exist and are acyclic, and the tracker is writable; mark issues whose scope is uncertain. Record the project path, Git branch, workspace baseline (modified/untracked/staged), and protectedPaths. Completion criterion: the DAG is valid, and the baseline and protection boundaries have been recorded.

2. Confirmation gate: display item by item according to the manifest fields (input sources, issue DAG,maxConcurrency、protectedPaths, evidence paths,maxRepairRounds), and wait for user confirmation. Before confirmation, do not create a team, do not start sub agents, and do not modify the tracker or workspace; only after confirmation, create one native AgentTeam and persist the manifest. Completion criterion: explicit user confirmation.

3. Frontier dispatch: each round, dispatch all issues on the frontier (dependencies verified resolved) concurrently within the maxConcurrency limit. The prompt follows context hygiene and contains only the issue ID, tracker file path,protectedPaths, exploration command, terminal-state format, and a one-line goal summary; the issue's original text is Read by the teammate itself. Each teammate calls only /wayfinderand explores only the current issue. Completion criterion: the entire frontier for this round is dispatched.

4. Independent verification: after a teammate reports a terminal state, the main Agent independently verifies the tracker's ## Answer、Status: resolved and reviewable evidence, and only after verification passes are successors unlocked. Issues that require code implementation or configuration changes remain blocked, with reason and evidence complete, awaiting user approval for subsequent handling. Failures propagate only along dependency descendants blocked, and independent branches continue. Completion criterion: all terminal states for this round are verified and written back to the tracker.

5. Wrap-up: after all child issues Status: resolved and have ## Answer and evidence, reclaim completed team tasks, and generate according to protocol the evidenceDir/report.md full details, outputting only a summary table in the conversation (issue / status / one-line conclusion) plus the report path. Completed issues are not started again. Completion criterion: report.md is persisted and the summary table has been output.

References

• Public protocol (manifest fields, frontier, context hygiene, terminal state, verification, fail-closed):references/agent-team-protocol.md