Beans (Citum)

Citum Overlay

The beans prime guide is already injected into every session — no need to call it again. Use these project-specific rules on top of it:

• Before starting work: search for an existing bean with beans list --json -S "<terms>".
• When choosing what to start next: run bash .claude/skills/beans/bin/citum-bean next, then inspect the candidate with beans show --json <id>.
• Always create beans with an explicit type (-t bug | feature | task | epic | milestone).
• Keep bean checklists current while work is in progress (- [ ] → - [x]).
• Mark completed only when all checklist items are checked.
• When completing, append a ## Summary of Changes section.
• When scrapping, append a ## Reasons for Scrapping section.
• Use upstream bean lifecycle names consistently: draft, todo, in-progress, completed, scrapped.
• When work lands on main, complete the bean in the same change series or immediate follow-up.
• Archive terminal beans promptly so completed and scrapped beans do not remain at .beans/ root.
• When bean state changes, run bash .claude/skills/beans/bin/citum-bean hygiene before push.
• If hygiene reports a stale bean, fix the bean metadata first, then rerun hygiene.