# Chips

Run the project's suggested-task ledger, the chips.

- Repository: https://github.com/udecode/dotai (1161 stars)
- Category: Git and review
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add udecode/dotai --skill chips -g -a claude-code -y`
Codex: `npx skills add udecode/dotai --skill chips -g -a codex -y`
Cursor: `npx skills add udecode/dotai --skill chips -g -a cursor -y`
Gemini CLI: `npx skills add udecode/dotai --skill chips -g -a gemini-cli -y`

## Description

Run the project's suggested-task ledger, the chips. /chips alone brings this session's open tasks up to date: it applies what the ledger helper says, settles stale and split tasks, cards what can start and reports the board, and /chips all also takes the ship-list tasks and the ones no live session owns. Use for /chips, /chips offer, start or drop, \"what chips are open\", \"suggest a task for X\", \"update the chips\", \"clean up the chips\", \"which chips are stale\", at the last hand-back of a run that offered a task, and whenever pstack would file a tracked issue, a follow-up, a reflect Backlog item or an out-of-band PR.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Chips

Chips are a project's suggested tasks, the side work outside a run's target, or a measurement that does not fit a run's one-hour budget, that the owner can start in a new session. They live as rows in one ledger per project, and a card in a suggest tool is only a view of one. The law is `.agents/pstack/rules/chips.md`, which sync-pstack renders into every project. Read it in full before this session's first ledger write, except in a session a card started, whose brief holds what its own task's rows need. This skill runs its modes; it adds no rule of its own.

Every command below is `node .agents/pstack/decisions-check.mjs <command>`, run from the project's checkout, which a card session that opened in its own worktree names by the path its brief prints. In a trunk project, where every session works in its own worktree, every command runs as written from that worktree, because the helper switches to the main checkout on its own for `chips` and for an `append` to the ledger. Get this session's id from the runtime's session tool, such as Claude Code desktop's `get_session` with `self`, and pass `--session <id>` to every board read. A runtime with no session tool reads the board without it.

| Mode | Use it to |
| --- | --- |
| [Sweep](#sweep), `/chips` with no argument, `/chips all` or `/chips codex` | bring this session's open tasks up to date, card what can start and report the board; `all` also lists every priority and takes the ship-list tasks and the tasks no live session owns, and `codex` forces the Codex handoff on each card it offers, outside trunk delivery |
| [Offer](#offer) | add a finding, the one way new work enters the ledger |
| [Close](#close) | card the run's own Ready offers at its last hand-back, without the sweep |
| [Start](#start) | begin a task a card opened, in the card's session |
| [Drop](#drop) | record the owner's word to drop a task |

The rest: https://github.com/udecode/dotai/blob/HEAD/skills/chips/SKILL.md