trackboi

Coordinates durable repo work with kanban boards and persistent context for humans and agents.

Updated May 11, 2026

Search Tags:#project memory #task tracking #kanban #MCP tools #decision logs #repo coordination

Ready to run

npx skills add https://github.com/b08x/rubysmithingV1 --skill trackboi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trackboi
Source: https://github.com/b08x/rubysmithingV1/tree/main/.agents/skills/trackboi
Command: npx skills add https://github.com/b08x/rubysmithingV1 --skill trackboi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

trackboi eliminates lost context and duplicated effort during multi-agent or multi-session repo work by keeping decisions and task progress in durable, repo-bound records.

Core Features & Use Cases

Durable project memory (Tracks): store summaries, decisions, references, and linked docs that persist across time and agents.
Executable task coordination (Cards): represent concrete work items, track status movement across columns, and capture progress updates.
Local-first orchestration with optional MCP integration: use trackboi MCP tools when available to create/update tracks and cards, while safely treating filesystem trackboi stores as read-only unless explicitly editing trackboi itself.

Quick Start

Use the trackboi skill to orient your agent to the active MCP context by requesting orient_agent when the trackboi MCP tools are available.

Frequently Asked Questions about trackboi

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

FAQPage Schema

How do I persist project context and task tracking across multiple agent sessions?▼

Durable project context and task tracking persist across sessions by storing decisions, summaries, and references in repo-bound records called Tracks, with concrete work items managed as Cards on a kanban board.

What's the best way to maintain durable kanban task tracking for multi-agent repo work?▼

Durable kanban task tracking for multi-agent repo work is maintained by coordinating status movement across columns using Cards, while keeping decisions and linked references in persistent Tracks to eliminate duplicated effort.

How does project memory coordinate with the filesystem when using MCP tools?▼

Project memory coordination uses MCP tools to perform all mutations for creating and updating tracks and cards, while safely treating filesystem trackboi stores as read-only context unless explicitly editing trackboi itself.

Do I need to run agent discovery before creating task cards and decision logs?▼

Agent discovery is required before creating task cards and decision logs; you must request orient_agent to orient your agent to the active MCP context and link cards to tracks when appropriate.

Can I use kanban board coordination for debugging, code review, and release migrations?▼

Kanban board coordination applies to implementation, debugging, review, handoffs, release/migration, cleanup, and blocker/decision tracking that must survive across sessions and multiple agents.

Why does my multi-session repo work lose context without persistent decision logs?▼

Multi-session repo work loses context without persistent decision logs because transient task progress and references are not bound to the repository, causing duplicated effort and lost decisions across agents.