backlog

You can prioritize a project backlog automatically by applying rule-based triage scoring that evaluates task staleness, dependency chains, and goal alignment. The scoring mechanism evaluates these factors to rank open items and reduce accumulated project debt.

The best way to maintain an auditable history is to store all technical debt and research tasks in a persistent markdown file as the single source of truth. The backlog skill manages this by recording item origins, approval decisions, and final resolution rationales.

To add and triage new backlog items, use a structured workflow that proposes items with deterministic numbering and origin details, then scores them by alignment to project goals. This ensures new items are evaluated consistently before interactive approval writes them to the persistent state.

Yes, structured backlog management requires interactive approval before any modification to the project state. The backlog skill enforces explicit user confirmation prior to writing new items, triage scores, or closure records to the persistent markdown file.

Yes, you can generate a concise, auditable status report summarizing open versus resolved project tasks. The backlog reporting feature compiles current item states, allowing you to review project debt and track completion progress across software and research workflows.

You should use rule-based task prioritization for software projects when managing technical debt, feature proposals, and research tasks requires consistent evaluation. It is ideal when you need automatic scoring by staleness and dependency to reduce project debt systematically.