Skip to content

Map: Implement the wayfinder ticket surface in legit #123

Description

@mayfieldiv

Destination

All eight implementation issues merged to main and the ticket surface usable end-to-end in the real TUI: t toggles into a queue reading this repo's GitHub maps and local efforts, with a detail page and p copy of the handoff prompt.

Notes

  • Execution map: this overrides wayfinder's plan-only default. Every ticket is a task; resolving one means implementing it — /implement driving /tdd — on a branch, /matt-code-review against the ticket, a PR opened only with explicit user approval (legit house rule), merged, then the ticket closed with a resolution comment linking the PR.
  • The spec is the resolution comment on Assemble the implementation-ready spec; CONTEXT.md's ### Wayfinder tickets section is the vocabulary; read AGENTS.md before any session.
  • Claim by assignee before any work. Native dependencies are the frontier; when a ticket closes, label the newly unblocked ones ready-for-agent.
  • Decisions surfaced during implementation that the spec doesn't settle: small ones resolve in the ticket and are noted in its resolution; anything that changes the spec gets a grilling ticket added here, not a silent deviation.
  • Planning history: Map: Wayfinder ticket surface in legit (closed).

Decisions so far

Not yet specified

None.

Out of scope

  • Ticket↔PR links — Surface links between wayfinder Tickets and PRs, its own effort.
  • Everything the planning map ruled out: interleaving tickets into the PR list, prompt-template customization, TUI write actions, GitLab, amending wayfinder conventions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions