Imported from BFalquet/AutoWork (.claude/skills/issue-board/SKILL.md). Install upstream with npx skills add BFalquet/AutoWork --skill issue-board. Copyright stays with the author.

issue-board

Name: issue-board
Author: BFalquet

The board is the memory. If it is stale, every later decision is wrong.

Where things live

.agent/projects/<project>/issues/<PREFIX>-<n>.md
.agent/projects/INDEX.md

Creating an issue

Copy .agent/templates/issue.md. Next number = highest existing + 1; never reuse. Acceptance criteria are the contract with the verifier — write them as statements that are true or false, not as tasks.

Bad: - handle errors properly Good: - a 429 response retries up to 3 times with exponential backoff Good: - pytest -q passes with no new warnings

Updating status

Edit the frontmatter, and only ever in this order of allowed moves:

todo → ready → doing → review → done
                 ↑        │
                 └─ rework┘        anything → blocked

Every transition writes something:

moving to	also set
`doing`	`branch`, `worktree`, `attempt`, `started`
`review`	`report:` path
`rework`	bump `attempt`, `verdict:` path, findings appended to the brief
`done`	`verdict:`, `merged_into:`
`blocked`	`blocked_reason:` — one sentence, concrete

Keeping the index honest

After any batch of changes, rewrite the counts in .agent/projects/INDEX.md. It is a summary, not a second source of truth — recount from the issue files, do not increment from memory.

Reporting status to the user

Compact table, most urgent first. Blocked items always shown, with the reason. Do not list done issues from previous runs unless asked.

{ "ocm": "1", "id": "bfalquet-autowork-issue-board", "kind": "skill", "name": "issue-board", "description": "Create, read, and update issue files and the project index so the board always reflects reality. Use when asked about project status, open issues, what is in flight, or when an issue's state changes during a run.", "publisher": "BFalquet", "version": "1.0.0", "capabilities": { "domains": [ "travel" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Create, read, and update issue files and the project index so the board always reflects reality. Use when asked about project status, open issues, what is in flight, or when an issue's state changes during a run." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/BFalquet/AutoWork", "path": ".claude/skills/issue-board/SKILL.md", "ref": "692e7e9329bcc847058653d3d084efe3756f2e21", "url": "https://github.com/BFalquet/AutoWork/blob/692e7e9329bcc847058653d3d084efe3756f2e21/.claude/skills/issue-board/SKILL.md", "key": "BFalquet/AutoWork/.claude/skills/issue-board/SKILL.md" } }, "instructions": "# issue-board\n\nThe board is the memory. If it is stale, every later decision is wrong.\n\n## Where things live\n\n```\n.agent/projects/<project>/issues/<PREFIX>-<n>.md\n.agent/projects/INDEX.md\n```\n\n## Creating an issue\n\nCopy `.agent/templates/issue.md`. Next number = highest existing + 1; never reuse.\nAcceptance criteria are the contract with the verifier — write them as statements\nthat are true or false, not as tasks.\n\nBad: `- handle errors properly`\nGood: `- a 429 response retries up to 3 times with exponential backoff`\nGood: `- pytest -q passes with no new warnings`\n\n## Updating status\n\nEdit the", "cost": { "context_tokens": 379 } }

issue-board

About

issue-board

Where things live

Creating an issue

Updating status

Keeping the index honest

Reporting status to the user

Use it

Manifest

Reviews