konradandCursor
3a49d52681
A failed open can repair the shell, and the installed PWA matches Ziele, Einstellungen, and the view download. Co-authored-by: Cursor <cursoragent@cursor.com>
31 lines
2.3 KiB
Markdown
31 lines
2.3 KiB
Markdown
# Issue tracker: Local Markdown
|
|
|
|
Issues and specs for this repo live as markdown files in `.scratch/`.
|
|
|
|
## Conventions
|
|
|
|
- One feature per directory, named with the local date and time when it is created: `.scratch/<YYYY-MM-DD>_<HH-mm>-<feature-slug>/`. Example: `.scratch/2026-10-09_07-31-einstellungen-und-ziele/`. The clock is 24-hour local time. Every new directory directly under `.scratch/` starts with that prefix, including wayfinding efforts.
|
|
- The spec is `.scratch/<YYYY-MM-DD>_<HH-mm>-<feature-slug>/spec.md`
|
|
- Implementation issues are one file per ticket at `.scratch/<YYYY-MM-DD>_<HH-mm>-<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
|
|
|
|
## When a skill says "publish to the issue tracker"
|
|
|
|
Create a new file under `.scratch/<YYYY-MM-DD>_<HH-mm>-<feature-slug>/` (creating the directory if needed). Take the date and time at the moment the directory is created. Do not invent a second prefix for files added later inside that directory.
|
|
|
|
## 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.
|
|
|
|
## Wayfinding operations
|
|
|
|
Used by `/wayfinder`. The **map** is a file with one **child** file per ticket.
|
|
|
|
- **Map**: `.scratch/<YYYY-MM-DD>_<HH-mm>-<effort>/map.md` (the Notes / Decisions-so-far / Fog body).
|
|
- **Child ticket**: `.scratch/<YYYY-MM-DD>_<HH-mm>-<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/<YYYY-MM-DD>_<HH-mm>-<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`.
|