droboticflow/docs/agents/issue-tracker.md

1.4 KiB

Issue tracker: Local Markdown

Issues and specs live as Markdown files in .scratch/.

Conventions

  • One feature per directory: .scratch/<feature-slug>/.
  • Spec: .scratch/<feature-slug>/spec.md.
  • One file per implementation ticket: .scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered from 01.
  • Record triage state as a Status: line near the top. Use the role strings in triage-labels.md.
  • Append discussion under ## Comments.

Publish and fetch

When a skill says "publish to the issue tracker", create the appropriate file under .scratch/<feature-slug>/, creating directories as needed.

When a skill says "fetch the relevant ticket", read the referenced file.

Wayfinding operations

  • Map: .scratch/<effort>/map.md, with Notes, Decisions-so-far, and Fog.
  • Child ticket: .scratch/<effort>/issues/NN-<slug>.md.
  • Record ticket type with Type: research, prototype, grilling, or task.
  • Record dependencies with Blocked by: NN, NN.
  • A ticket is unblocked when every listed dependency is resolved.
  • Select open, unblocked, unclaimed tickets in numeric order.
  • Claim a ticket by saving Status: claimed before starting work.
  • Resolve it by appending ## Answer, setting Status: resolved, and adding a summary and link to the map's Decisions-so-far section.

The claimed and resolved statuses describe wayfinding execution; they are separate from the five triage roles.