skills.rest
czottmann
czottmannCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

issue-tracking-with-beans

Coordinate issue tracking across Beans and TodoWrite with Git-tracked audit trails.

Updated Aug 27, 2026
Search Tags:#workflow#checklists#project-management#audit-trail#task-tracking#persistent-memory#beans
One-click install
npx skills add https://github.com/czottmann/claude-code-stuff --skill issue-tracking-with-beans
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-tracking-with-beans
Source: https://github.com/czottmann/claude-code-stuff/tree/main/skills/issue-tracking-with-beans
Command: npx skills add https://github.com/czottmann/claude-code-stuff --skill issue-tracking-with-beans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use Beans to persist non-trivial work and maintain an audit trail, ensuring long-running tasks are remembered across sessions and context changes.

Core Features & Use Cases

  • Persistent memory: Capture task details in Beans for future sessions.
  • Checklist discipline: Update checklists as work progresses to provide recoverable checkpoints.
  • Clear conventions: Guidance on when to use Beans vs other systems.

Quick Start

Create a Beans task to start work, then update the task as you complete each step and commit changes that reflect the progress.

Frequently Asked Questions about issue-tracking-with-beans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain an audit trail for long-running work tasks?▼

Audit trails for work tasks are maintained by recording task details in Beans, a Git-tracked persistent memory system. Each update to a task creates a recoverable checkpoint in version control, enabling you to review what was completed and when across sessions.

When should I use Beans versus a todo list for project work?▼

Use Beans for non-trivial, multi-step tasks that need persistent memory and audit history across sessions. Use a todo list like TodoWrite for live, visible progress tracking. Beans provides the enduring record; TodoWrite mirrors current status.

How do I sync work between Beans and TodoWrite?▼

Coordinate work by creating tasks in Beans first, then mirroring them in TodoWrite. Update both systems as you progress through steps, committing Beans changes to maintain the audit trail while TodoWrite reflects live progress for immediate visibility.

Can I track discovered work and implementation decisions in the same system?▼

Yes. Beans captures both non-trivial tasks and discovered work during implementation, including explicit decisions about where to record tasks. This single system enforces consistent checkpoints and decisions about task placement across your workflow.

What happens if I update a task but forget to commit the changes?▼

Without committing, Beans changes remain uncommitted in your working directory and won't create an audit trail in Git. Commit after each completed step to ensure the audit trail is preserved and the task state is recoverable in future sessions.

Related Skills

Explore More Software Engineering Skills→
mikersaysmikersays

issue-init

Initialize a structured issue tracking system in a Git repository.

Community
Intermediate
openakitaopenakita
2.0k

complete-plan

Mark a multi-step plan as completed and generate a final execution summary report.

Community
Basic
maslennikov-igmaslennikov-ig
243

format-todo-list

Convert task lists into TodoWrite JSON with validated statuses and active forms.

Community
Basic
Paxeer-NetworkPaxeer-Network
3

executing-tasks-from-any-source

Execute tasks from GitHub issues and Basic Memory artifacts via a unified workflow.

Official
Advanced