tbd

Consolidate Git-native issue tracking, spec-driven planning, and knowledge injection for software workflows.

75|7|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/jlevy/tbd --skill tbd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tbd
Source: https://github.com/jlevy/tbd/tree/main/.claude/skills/tbd
Command: npx skills add https://github.com/jlevy/tbd --skill tbd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The tbd skill consolidates Git-native issue tracking (beads), spec-driven planning, and knowledge injection to speed up AI-driven software work by providing a unified, workflow-ready context for agents.

Core Features & Use Cases

  • Beads-based issue tracking with cross-session persistence and dependencies.
  • Spec-driven workflows: plan features, break them into beads, and implement systematically.
  • Knowledge injection: on-demand access to engineering guidelines, best practices, and research briefs.
  • Shortcuts and templates: code review, commits, PRs, and architectural planning to accelerate delivery.

Quick Start

Install the tbd CLI: npm install -g get-tbd@latest When starting a new project, run tbd setup --auto --prefix=<name> # prefix is REQUIRED and should be 2-8 alphabetic chars Run tbd setup --auto # existing tbd project Run tbd prime to restore full context after compaction

Frequently Asked Questions about tbd

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

FAQPage Schema
How do I consolidate issue tracking and spec-driven planning for AI agents?

You can consolidate issue tracking and spec-driven planning for AI agents by using a Git-native workflow that unifies beads-based issue tracking, feature specs, and knowledge injection into a single context window.

What is beads-based issue tracking and how does it work with AI workflows?

Beads-based issue tracking is a Git-native method that persists issues across sessions with dependency support. It works with AI workflows by breaking feature specs into implementable beads for systematic agent execution.

How do I set up spec-driven development for a new software project?

To set up spec-driven development for a new project, install the CLI tool and run the setup command with an auto flag and a required 2-8 character alphabetic prefix to initialize the tracking environment.

Can I restore agent context after a session compaction during code review?

Yes, you can restore full agent context after a session compaction by running a prime command, which reloads the necessary issue tracking, spec, and knowledge injection data back into the environment.

Does this spec-driven workflow require external dependencies or databases?

No external databases are required. The workflow relies entirely on Git-native issue tracking and local directories for scripts, references, and assets to inject engineering guidelines directly into the agent context.

Related Skills