issue-tracking-with-beans-and-linear

Coordinate task tracking across Beans, Linear, and TodoWrite systems.

Updated Aug 27, 2026

Search Tags:#epics #linear #cross-system #todowrite #visibility #audit-trail #beans

Ready to run

npx skills add https://github.com/czottmann/claude-code-stuff --skill issue-tracking-with-beans-and-linear

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-tracking-with-beans-and-linear
Source: https://github.com/czottmann/claude-code-stuff/tree/main/skills/issue-tracking-with-beans-and-linear
Command: npx skills add https://github.com/czottmann/claude-code-stuff --skill issue-tracking-with-beans-and-linear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate work across Beans (memory), Linear (human planning), and TodoWrite (live progress) to give a complete, auditable view of a project.

Core Features & Use Cases

Tri-system tracking: Use all three systems for different audiences and persistence needs.
Bidirectional linking: Maintain references across Beans, Linear, and TodoWrite.
Escalation path: Discover and escalate work between systems when needed.

Quick Start

Begin with a Beans task and a Linear ticket, then create a matching TodoWrite list and ensure bidirectional links are in place. Update progress across all three as work advances.

Frequently Asked Questions about issue-tracking-with-beans-and-linear

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

FAQPage Schema

How do I synchronize work across Beans, Linear, and TodoWrite?▼

Synchronize work across these three systems by linking Beans tasks to Linear tickets and TodoWrite items, then mirroring updates bidirectionally as progress advances. This maintains a complete audit trail across all platforms while keeping each system's role distinct: Beans for agent memory, Linear for human planning, TodoWrite for live progress tracking.

When should I escalate tasks from TodoWrite or Beans to Linear?▼

Escalate discovered work to Linear when scope expands, architectural decisions emerge, or security concerns arise. Use TodoWrite and Beans for live work and agent-recorded tasks, then promote to Linear tickets when human review, formal planning, or cross-team visibility becomes necessary.

Can I manage epics across Beans, Linear, and TodoWrite at the same time?▼

Yes. Create and link beans with TodoWrite items, maintain bidirectional references to Linear epics, and enforce commit hygiene across all three systems. This tri-system approach gives you persistent agent memory, user-visible progress, and human-facing project planning in one coordinated workflow.

What's the best way to track discovered tasks across multiple systems?▼

Record discovered tasks in Beans first, create matching TodoWrite items for live progress, then link to Linear tickets if formal scope or human decisions are needed. This escalation path ensures nothing is lost while keeping each system focused on its audience and persistence requirement.

Do I need all three systems, or can I use just Linear and TodoWrite?▼

All three serve different needs: Beans provides persistent agent memory for context recovery, TodoWrite tracks live work with visible progress, and Linear handles human-facing planning and decisions. Using all three gives you an auditable, complete view; omitting any creates blind spots in either memory, visibility, or planning.