chips
Chips
Chips are a project's suggested tasks, the side work outside a run's target 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. 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. 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, /chips with no argument |
bring every open task up to date, card what can start and report the board |
| Offer | add a finding, the one way new work enters the ledger |
| Start | begin a task a card opened, in the card's session |
| Drop | record the owner's word to drop a task |
pstack calls these modes too. Where a pstack step files a tracked issue, a follow-up or a reflect Backlog item, or puts an out-of-band fix in its own PR, the lead runs Offer instead. At each hand-back, after each compaction and at the close, it runs a quick sweep, which skips step 3. A question about open chips, such as "what's next" over side work, runs steps 1 and 6 and writes nothing.