Skill Tracer
Skills › Skills For Real Engineers › setup-matt-pocock-skills › issue-tracker-local.md

issue-tracker-local.md

30 lines · skills/engineering/setup-matt-pocock-skills/issue-tracker-local.md at 4ae2317

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# Issue tracker: Local Markdown
2
3Issues and specs for this repo live as markdown files in `.scratch/`.
4

Issue tracker: Local Markdown

Issues and specs for this repo live as markdown files in .scratch/.

Raw lines 1 to 4
5## Conventions
6
7- One feature per directory: `.scratch/<feature-slug>/`
8- The spec is `.scratch/<feature-slug>/spec.md`
9- Implementation issues are one file per ticket at `.scratch/<feature-slug>/issues/<NN>-<slug>.md`, numbered from `01`, never a single combined tickets file
10- Triage state is recorded as a `Status:` line near the top of each issue file (see `triage-labels.md` for the role strings)
11- Comments and conversation history append to the bottom of the file under a `## Comments` heading

Conventions

  • One feature per directory: .scratch/<feature-slug>/
  • The spec is .scratch/<feature-slug>/spec.md
  • Implementation issues are one file per ticket at .scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered from 01, never a single combined tickets file
  • Triage state is recorded as a Status: line near the top of each issue file (see triage-labels.md for the role strings)
  • Comments and conversation history append to the bottom of the file under a ## Comments heading
Raw lines 5 to 12
13## When a skill says "publish to the issue tracker"
15Create a new file under `.scratch/<feature-slug>/` (creating the directory if needed).

When a skill says "publish to the issue tracker"

Create a new file under .scratch/<feature-slug>/ (creating the directory if needed).

Raw lines 13 to 16
17## When a skill says "fetch the relevant ticket"
19Read the file at the referenced path. The user will normally pass the path or the issue number directly.

When a skill says "fetch the relevant ticket"

Read the file at the referenced path. The user will normally pass the path or the issue number directly.

Raw lines 17 to 20
21## Wayfinding operations
23Used by `/wayfinder`. The **map** is a file with one **child** file per ticket.
25- **Map**: `.scratch/<effort>/map.md` (the Notes / Decisions-so-far / Fog body).
26- **Child ticket**: `.scratch/<effort>/issues/NN-<slug>.md`, numbered from `01`, with the question in the body. A `Type:` line records the ticket type (`research`/`prototype`/`grilling`/`task`); a `Status:` line records `claimed`/`resolved`.
27- **Blocking**: a `Blocked by: NN, NN` line near the top. A ticket is unblocked when every file it lists is `resolved`.
28- **Frontier**: scan `.scratch/<effort>/issues/` for files that are open, unblocked, and unclaimed; first by number wins.
29- **Claim**: set `Status: claimed` and save before any work.
30- **Resolve**: append the answer under an `## Answer` heading, set `Status: resolved`, then append a context pointer (gist + link) to the map's Decisions-so-far in `map.md`.

Wayfinding operations

Used by /wayfinder. The map is a file with one child file per ticket.

  • Map: .scratch/<effort>/map.md (the Notes / Decisions-so-far / Fog body).
  • Child ticket: .scratch/<effort>/issues/NN-<slug>.md, numbered from 01, with the question in the body. A Type: line records the ticket type (research/prototype/grilling/task); a Status: line records claimed/resolved.
  • Blocking: a Blocked by: NN, NN line near the top. A ticket is unblocked when every file it lists is resolved.
  • Frontier: scan .scratch/<effort>/issues/ for files that are open, unblocked, and unclaimed; first by number wins.
  • Claim: set Status: claimed and save before any work.
  • Resolve: append the answer under an ## Answer heading, set Status: resolved, then append a context pointer (gist + link) to the map's Decisions-so-far in map.md.
Raw lines 21 to 30
Names a skill wayfinder :23
Names a skill research :26
Names a skill prototype :26
Names a skill grilling :26