# Agent Issue Tracker Setup

The default issue tracker for agent work in this repo is local project memory, not external GitHub issue writes.

## Default Tracker

- Use `zonegaze/memory/` for PRDs, issue-like slices, active status, blockers, verification evidence, and cross-chat handoff.
- For substantial work, create or update a compact `00-status.md` or `00-goal-status.md` under a focused `zonegaze/memory/<feature>/` folder.
- For small one-turn docs or code changes, the commit plus final response can be the closeout record when no future agent context would be lost.

## GitHub Issues

- Read GitHub issues when the user references an issue number or URL, following the root `AGENTS.md` rule to read all comments.
- Do not create, label, close, or comment on GitHub issues unless the task explicitly targets GitHub issue work or the user has clearly requested an external issue write.
- When a GitHub issue is the source of truth, include `fixes #<number>` or `closes #<number>` in the commit message only when the completed merge should close it.

## Matt Pocock Skill Adaptation

- `to-prd` should write PRDs to local project memory unless an external issue tracker is explicitly requested.
- `to-issues` should create local issue-like Markdown slices under `zonegaze/memory/<feature>/` by default.
- `triage` should classify local tracker items by status unless a GitHub issue/PR is explicitly in scope.
- `implement` should take one local slice at a time, create a fresh task branch/worktree from `development`, validate locally, merge to `development`, push `origin/development`, and clean the completed local branch/worktree.
