Planning help

How the board works, and how to get Claude to update it for you.

Using the board

• Priority: cards are in priority order, top is P1. Drag a card, or use its ↑ and ↓ buttons. Drag onto another column to move it to that bucket.
• Assign: type a name in the box at the bottom of a card. Names already in use are suggested.
• Open a ticket: click its title. Edit changes the title, summary, details (Markdown), state, games and the cannot-reproduce flag.
• Screenshots and files: with a ticket open, paste a screenshot (Cmd+V), drop files on it, or use Attach files. Up to 25 MB each.
• Closed tickets: set State to closed in the edit form. They move to the Closed tickets section under the columns, where you can search them and reopen them.
• Download: the buttons at the top save a read-only copy of the page or all the data as JSON.

Using Claude with the board

Open the planning repo in Claude Code and just say what you want. The repo's CLAUDE.md tells Claude how the board and the GitHub issues fit together, so you don't need to explain it.

• "What's open in bugs?"
• "Close #26. It was fixed in the wd1 config change."
• "Replace the details of #23 with this: …" (paste the new text)
• "File a bug: stream clicks fail in Covet Fashion. Here's what I saw: …"
• "Move #24 to features and assign it to Sam."
• "Attach this screenshot to #25." (give it the file path)

Claude changes the live board only when you ask it to, and says what it ran. Its edits show up as api:claude on the ticket. It also opens and closes the matching GitHub issue when that is part of what you asked.

One-time setup for Claude

1. Clone the repo: git clone https://github.com/OFC-Ads/planning.git, and open that folder in Claude Code.
2. Get the board's API token from a teammate. Share it privately, never in a ticket or chat.
3. Save it on your machine:

   mkdir -p ~/.config/planning-board && chmod 700 ~/.config/planning-board
   pbpaste > ~/.config/planning-board/token && chmod 600 ~/.config/planning-board/token

   (Copy the token first. On Linux use xclip -o instead of pbpaste.)
4. For GitHub issues, run gh auth login once with your work account.

Good to know

• The board is the source of truth for priority, assignee and state. The markdown files in bugs/ are only the starting copy, and editing them doesn't change the board.
• Tickets are backed up nightly, and the database can be restored to any minute in the last week or more. Attachment files are not backed up.
• Don't put passwords, tokens or personal data in a ticket.