Tbd
Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code. Invoke when user mentions: tbd, beads,
Install
npx skills add jlevy/simple-modern-uv --skill tbdgit clone --depth 1 https://github.com/jlevy/simple-modern-uv.git /tmp/simple-modern-uv
mkdir -p ~/.claude/skills
cp -r /tmp/simple-modern-uv/.agents/skills/tbd ~/.claude/skills/tbdPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
**`tbd` helps humans and agents ship code with greater speed, quality, and discipline.** 1. **Beads**: Git-native issue tracking (tasks, bugs, features). Never lose work across sessions. Drop-in replacement for `bd`. 2. **Spec-Driven Workflows**: Plan features → break into beads → implement systematically. 3. **Knowledge Injection**: 25+ engineering guidelines (TypeScript, Python, TDD, testing, Convex, monorepos) available on demand. 4. **Shortcuts**: Reusable instruction templates for common workflows (code review, commits, PRs, cleanup, handoffs). ## Installation ```bash npm install -g get-tbd@latest tbd setup --auto --prefix=<name> # Fresh project (--prefix is REQUIRED: 2-8 alphabetic chars recommended. ALWAYS ASK THE USER FOR THE PREFIX; do not guess it) tbd setup --auto # Existing tbd project (prefix already set) tbd setup --from-beads # Migration from .beads/ if `bd` has been used ``` ## Routine Commands ```bash tbd --help # Command reference tbd status # Status tbd doctor # If there are problems tbd setup --auto # Run any time to refresh setup tbd prime # Restore full context on tbd after compaction ``` ## CRITICAL: You Operate tbd — The User Doesn’t **You are the tbd operator:** Users talk naturally; you translate their requests to tbd actions. DO NOT tell users to run tbd commands. That’s your job. - **WRONG**: “Run `tbd create` to track this bug”
Details
- Skill name
tbd- Repository
- jlevy/simple-modern-uv
- Path
.agents/skills/tbd/SKILL.md- License
- MIT
- Repo updated
- 26 August 2026
FAQ
What does the Tbd skill do?
Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code. Invoke when user mentions: tbd, beads,
How do I install the Tbd skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jlevy/simple-modern-uv --skill tbd. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Tbd popular?
It lives in jlevy/simple-modern-uv, which has 307 GitHub stars and 32 forks.
Related skills
Simple Modern Uv
307jlevy/simple-modern-uv
Start, selectively modernize, fully migrate, or update Python projects using simple-modern-uv practices: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing. Use when creating a Python project; adding selected tooling or repository practices to an existing project; migrating from Poetry, setuptools, pip, requirements.txt, PDM, or hatch; or updating a project already managed by the simple-modern-uv Copier template.
Trade Journal
564agiprolabs/claude-trading-skills
Structured trade logging, performance review, behavioral pattern detection, and strategy attribution for systematic improvement
Obsidian
198gapmiss/obsidian-plugin-skill
Comprehensive guidelines for Obsidian.md plugin development including ESLint rules from eslint-plugin-obsidianmd v0.6.0, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, popout window compatibility, community.obsidian.md submission process, and Scorecard optimization. Use when working with Obsidian plugins, main.ts files, manifest.json, Plugin class, MarkdownView, TFile, vault operations, or any Obsidian API development.
01 Brainstorm
564ai-driven-dev/framework
Clarify a vague idea through questions. Use when the user has a half-formed idea, ambiguous request, or asks to brainstorm, discover, refine, or clarify. Not for artifact gap scans, planning, or code.
Skill Router
517dotslashsimran/simcraft
Decide which installed skill, or which chain of two or three skills, fits a task before starting it, and run them in the right order with each one's output feeding the next. Works with any set of skills, because it reads every installed skill's description at run time. Use when a task is big or vague, could fit several skills, or needs more than one ("which skill should I use", "what's the best way to do this", "plan the steps", "use whatever skills make sense"), or when it's unclear whether any skill applies.
01 Usage
564ai-driven-dev/framework
Answer what a period or one piece of work consumed in tokens, per day, model, agent, tool, task, ticket, session, repository or person, from the local measurement. Use when the user asks how many tokens were spent, where the effort went, or what a task or ticket consumed. Not for turning measurement on or off.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.