跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

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, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library, source code review, or any

jlevy · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add jlevy/simple-modern-uv --skill tbd

技能说明


allowed-tools: Bash(tbd:*), Read, Write description: |- 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, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library, source code review, or any workflow shortcut. name: tbd

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

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

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”

  • RIGHT: (you run tbd create yourself and tell the user it’s tracked)

Welcoming a user: When users ask “what is tbd?” or want help → run tbd shortcut welcome-user

User Request → Agent Action

User SaysYou (the Agent) Run
Issues/Beads
“There’s a bug where …”tbd create "..." --type=bug
“Create a task/feature for …”tbd create "..." --type=task or --type=feature
“Let’s work on issues/beads”tbd ready
“Show me issue X”tbd show <id>
“Close this issue”tbd close <id>
“Search issues for X”tbd search "X"
“Add label X to issue”tbd label add <id> <label>
“What issues are stale?”tbd stale
Planning & Specs
“Plan a new feature” / “Create a spec”tbd shortcut new-plan-spec
“Break spec into beads”tbd shortcut plan-implementation-with-beads
“Implement these beads”tbd shortcut implement-beads
Code Review & Commits
“Review this code” / “Code review”tbd shortcut review-code
“Review this PR”tbd shortcut review-github-pr
“Commit this” / “Use the commit shortcut”tbd shortcut code-review-and-commit
“Create a PR” / “File a PR”tbd shortcut create-or-update-pr-simple
“Merge main into my branch”tbd shortcut merge-upstream
Guidelines & Knowledge
(any engineering work)Load the General engineering group first (see below)
“Use TypeScript best practices”tbd guidelines typescript-rules
“Use Python best practices”tbd guidelines python-rules
“Build a TypeScript CLI”tbd guidelines typescript-cli-tool-rules
“Improve monorepo setup”tbd guidelines pnpm-monorepo-patterns or bun-monorepo-patterns
“Add golden/e2e testing”tbd guidelines golden-testing-guidelines
“Use TDD” / “Test-driven development”tbd guidelines general-tdd-guidelines
“Convex best practices”tbd guidelines convex-rules
Documentation
“Research this topic”tbd shortcut new-research-brief
“Document architecture”tbd shortcut new-architecture-doc
Cleanup & Maintenance
“Clean up this code” / “Remove dead code”tbd shortcut code-cleanup-all
“Fix repository problems”tbd doctor --fix
Sessions & Handoffs
“Hand off to another agent”tbd shortcut agent-handoff
“Check out this library’s source”tbd shortcut checkout-third-party-repo
(your choice whenever appropriate)tbd list, tbd dep add, tbd close, tbd sync, etc.

Loading guidelines for engineering work: Before writing or reviewing code, load the General engineering group—the general-* rules plus error-handling-rules—since these apply to all code regardless of language. Then load the group for the language or framework in use (TypeScript, Python, Convex, etc.). Run tbd guidelines --list to see all available guidelines.

Note: Never gitignore .tbd/workspaces/ — the outbox must be committed to your working branch. See tbd guidelines tbd-sync-troubleshooting for details.

CRITICAL: Session Closing Protocol

Before saying “done”, you MUST complete this checklist:

[ ] 1. git add + git commit
[ ] 2. git push
[ ] 3. gh pr checks <PR> --watch 2>&1 (IMPORTANT: WAIT for final summary, do NOT tell user it is done until 
阅读完整来源 ↗