burn

Executes claude:-marked doit todos autonomously in priority order with claim locks and completion notes.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/bearded-giant/claude-code-config --skill burn-bearded-giant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: burn
Source: https://github.com/bearded-giant/claude-code-config/tree/main/skills/burn
Command: npx skills add https://github.com/bearded-giant/claude-code-config --skill burn-bearded-giant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the manual overhead of working through a backlog of delegated tasks by autonomously draining doit todos that the user has assigned to the model with a claude: prefix, one priority-ordered item at a time. ## Core Features & Use Cases - Autonomous queue drain: Claims each claude:-marked todo via in_progress, works it end-to-end under normal git and confirmation gates, then marks it done with an appended completion record. - Priority-ordered execution: Burns items critical-first (critical → urgent → important → none), with --priority, --max, --list, and --dry-run flags for control. - Parallel-session safety: The in_progress claim acts as a lock so 4-6 concurrent sessions never double-grab the same item; blocked items are re-queued with a BLOCKED note. - Use Case: You tag five todos with claude: in your project's doit list before lunch, then run /burn — the model works each one, commits where authorized, and appends a timestamped DONE record to each todo's note. ## Quick Start Say "burn my todos" or invoke /burn to start draining the claude:-marked items from the current session's doit list.

Frequently Asked Questions about burn

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

FAQPage Schema
How do I assign a doit todo to Claude for autonomous execution?

Prefix the todo text with `claude:` (case-insensitive), for example `claude: fix token expiry check in auth middleware`. Put any doc links, scripts, or identifiers in the todo's note, and /burn will pick it up by priority.

How does /burn decide which doit list to work from?

It uses the repo-qualified, worktree-aware list name printed by the SessionStart hook (for example `claude-code-config-oauth-ttl`), or the bare repo name when no feature is set. The `--list <name>` flag overrides this with an explicit target.

Can multiple Claude sessions burn the same todo queue in parallel?

Yes. Each item is claimed via start_todo (in_progress) before any work begins, which acts as a lock so parallel sessions see it as taken and never double-grab. Completed items drop out of the pending queue automatically.

What happens when a burn item is blocked or destructive?

Blocked items get a BLOCKED note appended and are reverted to pending for re-queuing. Destructive, irreversible, or sev-5 items (data loss, security, production mutation) pause the run and are surfaced for human decision instead of being executed.

How do I run the burn queue on a recurring schedule?

Use `/loop 10m /burn` to drain the queue every ten minutes. The loop skill owns scheduling, and each /burn run is idempotent because claimed items are in_progress and completed items leave the pending queue.