tbd
starsforks
How to install tbd?
jlevy/simple-modern-uv/tbd
$npx -y skills add jlevy/simple-modern-uv --skill tbdGit-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, implement
SKILL.md
| 1 | <!-- DO NOT EDIT: Generated by tbd setup (format=f04). |
| 2 | Run 'tbd setup' to update. |
| 3 | --> |
| 4 | |
| 5 | **`tbd` helps humans and agents ship code with greater speed, quality, and discipline.** |
| 6 | |
| 7 | 1. **Beads**: Git-native issue tracking (tasks, bugs, features). |
| 8 | Never lose work across sessions. |
| 9 | Drop-in replacement for `bd`. |
| 10 | 2. **Spec-Driven Workflows**: Plan features → break into beads → implement |
| 11 | systematically. |
| 12 | 3. **Knowledge Injection**: 25+ engineering guidelines (TypeScript, Python, TDD, |
| 13 | testing, Convex, monorepos) available on demand. |
| 14 | 4. **Shortcuts**: Reusable instruction templates for common workflows (code review, |
| 15 | commits, PRs, cleanup, handoffs). |
| 16 | |
| 17 | ## Installation |
| 18 | |
| 19 | ```bash |
| 20 | npm install -g get-tbd@latest |
| 21 | 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) |
| 22 | tbd setup --auto # Existing tbd project (prefix already set) |
| 23 | tbd setup --from-beads # Migration from .beads/ if `bd` has been used |
| 24 | ``` |
| 25 | |
| 26 | ## Routine Commands |
| 27 | |
| 28 | ```bash |
| 29 | tbd --help # Command reference |
| 30 | tbd status # Status |
| 31 | tbd doctor # If there are problems |
| 32 | |
| 33 | tbd setup --auto # Run any time to refresh setup |
| 34 | tbd prime # Restore full context on tbd after compaction |
| 35 | ``` |
| 36 | |
| 37 | ## CRITICAL: You Operate tbd — The User Doesn’t |
| 38 | |
| 39 | **You are the tbd operator:** Users talk naturally; you translate their requests to tbd |
| 40 | actions. DO NOT tell users to run tbd commands. |
| 41 | That’s your job. |
| 42 | |
| 43 | - **WRONG**: “Run `tbd create` to track this bug” |
| 44 | |
| 45 | - **RIGHT**: *(you run `tbd create` yourself and tell the user it’s tracked)* |
| 46 | |
| 47 | **Welcoming a user:** When users ask “what is tbd?” |
| 48 | or want help → run `tbd shortcut welcome-user` |
| 49 | |
| 50 | ## User Request → Agent Action |
| 51 | |
| 52 | | User Says | You (the Agent) Run | |
| 53 | | --- | --- | |
| 54 | | **Issues/Beads** | | |
| 55 | | “There’s a bug where …” | `tbd create "..." --type=bug` | |
| 56 | | “Create a task/feature for …” | `tbd create "..." --type=task` or `--type=feature` | |
| 57 | | “Let’s work on issues/beads” | `tbd ready` | |
| 58 | | “Show me issue X” | `tbd show <id>` | |
| 59 | | “Close this issue” | `tbd close <id>` | |
| 60 | | “Search issues for X” | `tbd search "X"` | |
| 61 | | “Add label X to issue” | `tbd label add <id> <label>` | |
| 62 | | “What issues are stale?” | `tbd stale` | |
| 63 | | **Planning & Specs** | | |
| 64 | | “Plan a new feature” / “Create a spec” | `tbd shortcut new-plan-spec` | |
| 65 | | “Break spec into beads” | `tbd shortcut plan-implementation-with-beads` | |
| 66 | | “Implement these beads” | `tbd shortcut implement-beads` | |
| 67 | | **Code Review & Commits** | | |
| 68 | | “Review this code” / “Code review” | `tbd shortcut review-code` | |
| 69 | | “Review this PR” | `tbd shortcut review-github-pr` | |
| 70 | | “Commit this” / “Use the commit shortcut” | `tbd shortcut code-review-and-commit` | |
| 71 | | “Create a PR” / “File a PR” | `tbd shortcut create-or-update-pr-simple` | |
| 72 | | “Merge main into my branch” | `tbd shortcut merge-upstream` | |
| 73 | | **Guidelines & Knowledge** | | |
| 74 | | *(any engineering work)* | Load the **General engineering** group first (see below) | |
| 75 | | “Use TypeScript best practices” | `tbd guidelines typescript-rules` | |
| 76 | | “Use Python best practices” | `tbd guidelines python-rules` | |
| 77 | | “Build a TypeScript CLI” | `tbd guidelines typescript-cli-tool-rules` | |
| 78 | | “Improve monorepo setup” | `tbd guidelines pnpm-monorepo-patterns` or `bun-monorepo-patterns` | |
| 79 | | “Add golden/e2e testing” | `tbd guidelines golden-testing-guidelines` | |
| 80 | | “Use TDD” / “Test-driven development” | `tbd guidelines general-tdd-guidelines` | |
| 81 | | “Convex best practices” | `tbd guidelines convex-rules` | |
| 82 | | **Documentation** | | |
| 83 | | “Research this topic” | `tbd shortcut new-research-brief` | |
| 84 | | “Document architecture” | `tbd shortcut new-architecture-doc` | |
| 85 | | **Cleanup & Maintenance** | | |
| 86 | | “Clean up this code” / “Remove dead code” | `tbd shortcut code-cleanup-all` | |
| 87 | | “Fix repository problems” | `tbd doctor --fix` | |
| 88 | | **Sessions & Handoffs** | | |
| 89 | | “Hand off to another agent” | `tbd s |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
