bits
/bits
Track and manage work items, tasks, issues, and todos with dependencies using bits. Use when user needs to create tasks, track progress, manage blockers, find ready work, claim/release tasks, close completed work, or organize multi-step projects. Triggers on "bits", "task", "issue", "backlog", "blockers", "dependencies", "what's ready", "track this", "add to my list", "what should I work on".
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Track and manage work items, tasks, issues, and todos with dependencies using bits. Use when user needs to create tasks, track progress, manage blockers, find ready work, claim/release tasks, close completed work, or organize multi-step projects. Triggers on "bits", "task", "issue", "backlog", "blockers", "dependencies", "what's ready", "track this", "add to my list", "what should I work on".
Triggers from the description
Arguments
/bits [command or task description]
Original author description
Track and manage work items, tasks, issues, and todos with dependencies using bits. Use when user needs to create tasks, track progress, manage blockers, find ready work, claim/release tasks, close completed work, or organize multi-step projects. Triggers on "bits", "task", "issue", "backlog", "blockers", "dependencies", "what's ready", "track this", "add to my list", "what should I work on".
How it works
- Bits Are Immutable
- When to Use
- Commands
- Dependencies
- Session Commands
- Drain Commands
- Task Description Format
- Do NOT Close If
SKILL.md preview
--- name: bits description: Track and manage work items, tasks, issues, and todos with dependencies using bits. Use when user needs to create tasks, track progress, manage blockers, find ready work, claim/release tasks, close completed work, or organize multi-step projects. Triggers on "bits", "task", "issue", "backlog", "blockers", "dependencies", "what's ready", "track this", "add to my list", "what should I work on". user-invocable: false argument-hint: "[command or task description]" allowed-tools: - Bash(bits:*) - Bash(git:*) - Read --- # Bits Task Tracking ## Bits Are Immutable Once created, bits cannot be updated. This means: - **No checkboxes** in descriptions (you can't check them off) - **No sub-tasks** in descriptions (you can't mark them complete) - **No progress tracking** within a single bit **Instead:** Create more bits. They're free. Break work into atomic pieces and link them with dependencies using `bits dep <id> <blocker-id>`. ```bash # Bad: One bit with checkboxes bits add "Implement auth" -d "- [ ] Add login\n- [ ] Add logout\n- [ ] Add session" # Good: Multiple linked bits bits add "Add login endpoint" -d "POST /login with JWT" --json bits add "Add logout endpoint" -d "POST /logout invalidates token" --json bits add "Add session middleware" -d "Validate JWT on protected routes" --json bits dep <logout-id> <login-id> bits dep <session-id> <login-id> ``` ## When to Use | Scenario | Tool | |----------|------| | Multi-step work with dependencies | bits | | Tasks that block other tasks | bits | | Tracking progress across sessions | bits | | Simple one-off checklist | TaskCreate | | Quick session-scoped todos | TaskCreate | ## Commands | Task | Command | |------|---------| | Find ready work | `bits ready --json` | | Create task | `bits add "Title" -d "Description" --json` | | Start work | `bits claim <id>` | | Pause work | `bits release <id>` | | Complete work | `bits close <id> "reason"` | | View details | `bits show <id>` | | List tasks | `bits list` | Run `bits --help` for full reference. ## Dependencies ```bash bits add "Feature B" --json # Returns: bits-abc123 bits dep bits-abc123 bits-blocker # B blocked by blocker ``` Tasks with unresolved dependencies won't appear in `bits ready`. ## Session Commands | Command | Purpose | |---------|---------| | `bits session claim` | Claim primary session (reads stdin) | | `bits session release` | Release session (reads stdin) | | `bits session prune` | Manual cleanup of stale sessions | | `bits session hook` | Stop hook with session ownership check | | `bits session compact` | Output drain context after compaction (for hooks) | ## Drain Commands | Command | Purpose | |---------|---------| | `bits drain claim` | Activate drain mode | | `bits drain release` | Deactivate drain mode (fails if tasks remain) | | `bits drain release --force` | Suspend drain mode (for replan/escalation) | ## Task Description Format ```markdown # Context What this task solves and why. # Acceptance Criteria Concrete conditions that must be true when done: - Criterion 1 - Criterion 2 # Verification Commands - `mise run lint` - `mise run test` ``` Do not use checkboxes in descriptions — bits are immutable so checkboxes cannot be checked off. State criteria as plain text. ## Do NOT Close If - Tests failing - Implementation partial - Unresolved errors Instead: Create new blocker bits and add them as dependencies.
Versions
The database has no other skills named bits.
Database snapshot: 13.11.2026 · package version 9752ea72689b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100bits-plan
Analyze conversation history and create bits tasks with dependencies. Use when extracting work from a discussion, turning decisions into tracked tasks, or breaking down what was discussed into actionable items. Triggers on "create tasks from this", "turn this into bits",… - 100planning
Create structured plan documents and track work items using YAML frontmatter. Use when the user wants to plan a feature, track progress, log bugs/tasks/ideas, or organize project work. - 90workspace-assistant
This skill should be used when the user asks to create quick tasks, log bugs, track one-off work items, or manage tasks in the default project. Triggers on phrases like 'add a task', 'log a bug', 'track this', 'create a quick task', 'update task status'. - 100todo
Add, complete, view, or link plans to items in the project backlog (GitHub issues or brain/todos.md). Use when the user says "todo", "add a todo", "mark done", "what's on the backlog", "show todos", "list tasks", "check off", or wants to manage their task list. - 96task
Manage the project task backlog as plain markdown files in tasks/. Use when the user asks to list or query existing tasks, to update or expand one, to triage or split backlog items, or to work across several tasks at once, and as the fallback for any tasks, todos, or backlog… - 100beads
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect…