Task Review And Context Keeper: Keep your vibe coding on track
You can install this plugin from any of these themed marketplaces. Choose one, add it as a marketplace, then install the plugin.
Choose your preferred installation method below
A marketplace is a collection of plugins. Every plugin gets an auto-generated marketplace JSON for individual installation, plus inclusion in category and themed collections. Add a marketplace once (step 1), then install any plugin from it (step 2).
One-time setup for access to all plugins
When to use: If you plan to install multiple plugins now or later
Step 1: Add the marketplace (one-time)
/plugin marketplace add https://claudepluginhub.com/marketplaces/all.jsonRun this once to access all plugins
Step 2: Install this plugin
/plugin install cc-track-2@allUse this plugin's auto-generated marketplace JSON for individual installation
When to use: If you only want to try this specific plugin
Step 1: Add this plugin's marketplace
/plugin marketplace add https://claudepluginhub.com/marketplaces/plugins/cc-track-2.jsonStep 2: Install the plugin
/plugin install cc-track-2@cc-track-2Task Review And Context Keeper - Keep your vibe coding on track
cc-track is a comprehensive context management and workflow optimization system for Claude Code. It solves the fundamental problem of context loss in AI-assisted development by providing intelligent task tracking, automatic validation, and persistent memory across sessions.
When working with Claude Code, you face several challenges:
cc-track solves these problems by:
cc-track is distributed as a Claude Code plugin. Installation is a one-time setup that makes cc-track available to all your projects.
# 1. Add the cc-track marketplace
/plugin marketplace add cahaseler/cc-track-marketplace
# 2. Install the plugin
/plugin install cc-track@cc-track-marketplace
# 3. Install plugin dependencies
cd $(dirname $(which claude-code))/../plugins/cc-track
bun install
# 4. Navigate to your project and run setup
cd /path/to/your-project
/setup-cc-track
The /setup-cc-track command guides you through configuration:
curl -fsSL https://bun.sh/install | bashVerify Bun installation:
bun --version # Should show 1.0.0+
If you previously used the npm-distributed version (v2.x), see MIGRATION.md for step-by-step instructions.
Quick migration:
# Uninstall npm version
npm uninstall -g cc-track
# Install plugin (follow Quick Start above)
# Your .claude/ project files work unchanged!
When you run /setup-cc-track, Claude guides you through setup:
cc-track maintains several context files that Claude automatically references:
Claude's training data can make it default to searching for outdated years. The WebSearch validation hook catches this and helps you get current information:
What it blocks:
"TypeScript best practices 2024" → Suggests "TypeScript best practices 2025""2024 web development trends" → Suggests "2025 web development trends""latest 2024 React features" → Suggests "latest 2025 React features"What it allows:
"compare 2024 vs 2025 features" (intentional comparison)"2024 election results" (historical event)"bugs fixed in 2024" (temporal reference)When blocked, you receive clear feedback with:
Enable in .claude/track.config.json:
{
"features": {
"websearch_validation": {
"enabled": true
}
}
}
After setup, cc-track uses two configuration files:
.claude/track.config.jsonControls which features are enabled:
{
"capture_plan": true,
"stop_review": true,
"edit_validation": false,
"statusline": true,
"git_branching": true,
"github_integration": {
"enabled": true,
"auto_create_issues": true,
"use_issue_branches": true,
"auto_create_prs": true
}
}
.claude/settings.jsonClaude Code's hook configuration (managed by cc-track based on your config)
All cc-track functionality is accessed through slash commands in Claude Code:
/setup-cc-track - Initial setup wizard (verifies dependencies, configures features)/specify - Create new feature specification through Socratic questioning/clarify - Refine requirements and resolve ambiguities/plan - Generate technical implementation plan/tasks - Create task breakdown from plan/prepare-completion - Validate task readiness (tests, lint, code review)/complete-task - Complete task and create PR/add-to-backlog - Add items to backlog without disrupting current work/constitution - Create or update project guardrails/config-track - Modify feature configurationAfter initialization, cc-track creates:
your-project/
├── .claude/
│ ├── commands/ # Slash commands
│ ├── tasks/ # Task files (TASK_001.md, etc.) - structured files generated from plans
│ ├── plans/ # Captured plans - raw outputs from planning mode
│ ├── track.config.json # Feature configuration
│ ├── product_context.md # Project vision
│ ├── system_patterns.md # Technical patterns
│ ├── decision_log.md # Architectural decisions
│ ├── code_index.md # Codebase map
│ └── user_context.md # User preferences
└── CLAUDE.md # Main context file with imports
cc-track is designed to be:
cc-track uses Claude Code's plugin system for distribution and execution.
All slash commands reference the plugin directory using the ${CLAUDE_PLUGIN_ROOT} environment variable:
# Example command in commands/complete-task.md
!bun run ${CLAUDE_PLUGIN_ROOT}/commands/complete-task.ts
This ensures commands work regardless of where the plugin is installed. The variable is automatically provided by Claude Code.
The plugin runs TypeScript directly via Bun (no compilation needed):
hooks/hooks.json, executed by Claude Code's hook systemcc-track-plugin/
├── .claude-plugin/ # Plugin metadata
│ └── plugin.json
├── commands/ # Slash command markdown + TypeScript implementations
├── hooks/ # Hook TypeScript files + registration config
├── lib/ # Shared libraries
├── scripts/ # Statusline and other scripts
└── templates/ # Reference templates (not copied to projects)
To contribute or run from source:
# Clone the repository
git clone https://github.com/cahaseler/cc-track.git
cd cc-track
# Install dependencies
bun install
# Run tests
bun test
Note: There's no build step - TypeScript is executed directly via Bun.
MIT
3.0.0