Skip to content

Adopt wayfinder skill as the exploration on-ramp #691

Description

@bracyw

What

Adopt Matt Pocock's wayfinder: plan a huge, foggy effort as a shared map of investigation tickets on the tracker, resolved one at a time until the way to the destination is clear. Per Matt's own router it's an on-ramp, not the spine — it merges onto the main flow at to-spec (one map can feed many specs).

Scope

  • .claude/skills/wayfinder/SKILL.md, Argos-adapted: point at docs/agents/issue-tracker.md, keep HITL/AFK vocabulary.
  • Wayfinding operations section in issue-tracker.md (GitHub flavor: map issue, sub-issues, native dependencies + fallback, frontier query, claim, resolve).
  • Document the wayfinder:map / research / prototype / grilling / task labels.
  • Glossary terms (destination, map, frontier, fog of war, ticket types).
  • CLAUDE.md flow wiring: foggy/multi-session effort to wayfinder; single clear feature to grill to to-spec to to-tickets to implement.

Acceptance criteria

  • wayfinder skill loads
  • Wayfinding operations documented for GitHub
  • Flow narrative in CLAUDE.md reflects wayfinder as on-ramp merging at to-spec

Depends on the grilling/domain-modeling split (#684) and research (#689). Part of the Matt-Pocock-skills sync.

Metadata

Metadata

Assignees

No one assigned

    Labels

    DevOpsMaking development work smootherai-workflowTicket about the AI dev workflow itself (skills, docs/agents, issue pipeline), not product codemediumA more complex tasknew featureNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions