The caj-issues skill

---
name: caj-issues
description: Work with this project's caj board — open an issue when a question you can't answer arises during implementation, move issues between states with a highlight, and discuss decisions with the team. Use when you hit a question only a teammate can settle, or when the user asks to file/move/check a caj issue.
---

# caj issues

<!-- TODO(copy): one-paragraph framing of the workflow, in the author's voice. -->

caj tracks the questions that come up while building software. When you hit a
decision you can't settle yourself, open an issue so teammates can weigh in.
The board has four columns, and issues move freely between them:

- `needs_expertise` — a question someone on the team needs to answer
- `needs_implementation` — the decision is made; code needs writing
- `needs_review` — the work needs a teammate's eyes
- `done`

## Connect

The board is served over MCP at `https://codeasjunk.com/mcp`, authenticated by
an API token (create one on the tokens page). Register it once:

```sh
claude mcp add --transport http caj https://codeasjunk.com/mcp --header "Authorization: Bearer <token>"
```

## Tools

- `create_issue` — open an issue. `project` takes the repo you're working in
  (`owner/repo` or the git origin URL) or a `prj_` id. Give a `highlight`: the
  question you're stuck on, as the card should show it on the board.
- `move_issue` — move an issue to a new column. Always write a `highlight`
  saying what the card should show there (what you're stuck on, what to
  review).
- `comment_issue` — add to an issue's thread.
- `list_issues` — a project's issues, optionally one column.
- `get_issue` — one issue with its full comment and transition history.

## When to open an issue

<!-- TODO(copy): the author's guidance on what makes a good issue. -->

Open one when a question arises that you can't answer on your own — a design
choice with real trade-offs, a product decision, missing domain knowledge. Put
the question itself in the highlight. Don't open issues for things you can
settle by reading the code.

The free tier allows 10 new issues per project per UTC day; the daily-limit
error says when it resets.