burn-down

Process prioritized task backlogs within token or time budgets.

1|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/cdrguru/portable-agent-kit --skill burn-down
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: burn-down
Source: https://github.com/cdrguru/portable-agent-kit/tree/main/.agent/skills/burn-down
Command: npx skills add https://github.com/cdrguru/portable-agent-kit --skill burn-down

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates autonomous processing of a prioritized task backlog within a token or time budget, enabling productive work before resets.

Core Features & Use Cases

  • Autonomous backlog execution: prioritizes and completes tasks within the given budget, maximizing value.
  • Phase-aware planning: adapts work pace and task selection based on remaining context and budget phases (Sprint, Steady, Wind-down).
  • Commit-after-each-task: logs progress by committing after every completed task to preserve state and enable safe interruption.

Quick Start

Provide your current backlog and budget, and initiate the burn-down process to auto-execute top-priority tasks.

Frequently Asked Questions about burn-down

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

FAQPage Schema
How do I autonomously process a task backlog within a token or time budget?

Autonomous backlog processing within a token or time budget is handled by prioritizing tasks and executing them sequentially. The burn-down process adapts work pace based on remaining context and commits after each task to preserve state.

What is phase-aware planning for sprint task execution?

Phase-aware planning for sprint task execution adapts work pace and task selection based on remaining context and budget phases. It organizes autonomous backlog processing into Sprint, Steady, and Wind-down phases to maximize value before resets.

How do I auto-execute top-priority tasks during end-of-week sessions?

To auto-execute top-priority tasks during end-of-week sessions, you provide your current backlog and budget to initiate the burn-down process. The system autonomously processes tasks within the defined time or token constraints.

Can I safely interrupt autonomous backlog processing without losing progress?

You can safely interrupt autonomous backlog processing because the system commits after every completed task. This per-task commit logging preserves state and enables safe interruption at any phase boundary during sprint planning or time-boxed work.

Does burn-down task execution work for time-boxed sprint planning?

Burn-down task execution is designed specifically for time-boxed sprint planning and end-of-week sessions. It applies phase boundaries and budget parsing to ensure remaining work is completed within the allocated token or time constraints.

What are the limitations of autonomous backlog processing within token budgets?

Autonomous backlog processing within token budgets is limited by the defined time or token constraints, requiring tasks to be sized appropriately. Work must adapt to remaining context across phase boundaries, and incomplete tasks remain if the budget is exhausted.