Skip to content
Pathfinder

setup-tracker

Configure a work tracker only when the human asks.

Pathfinder works normally without one.

Process

  1. Ask where work should be tracked:
    • GitHub Issues
    • local Markdown files
    • another tracker the human describes
  2. Ask only for the information needed to use that tracker.
  3. Check where the approved Feature specs live. Ask only when they are not in context/features/; when the default is what the repository has, record it and move on.
  4. Create a proposed context/tracker.md naming, at minimum:
    • the tracker and how an agent reaches it
    • the spec source
    • how a published item records its Pathfinder key, so a later run recognises the item it published last time
  5. Show it to the human.
  6. Write it only after approval.

If context/tracker.md already exists, modify only the requested settings.

Rules

  • Do not publish or create work items.
  • Do not create labels, tags, or tracker conventions unless requested.
  • Do not add dependencies or tracker-specific code.
  • Feature specs remain canonical.
  • Tracking is always optional.

Publishing belongs to sync-tracker.

Stop after configuration.