backlog

Reconcile bugs and opportunities with code and update canonical docs indexes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cirne/brain-app --skill backlog-cirne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/cirne/brain-app/tree/main/.cursor/skills/backlog
Command: npx skills add https://github.com/cirne/brain-app --skill backlog-cirne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains brain-app bug and opportunity hygiene—reconciles docs with code, archives completed work, files new items, and updates unified docs/BUGS.md + docs/OPPORTUNITIES.md. Use when the user invokes /backlog, asks to triage bugs or opportunities, review the backlog, archive fixed issues, or align tracking docs with reality.

Core Features & Use Cases

  • Centralizes active bugs in docs/bugs and active opportunities in docs/opportunities, and updates the main indexes.
  • Archives completed items to the archive subfolders and preserves history for traceability.
  • Keeps canonical references and links consistent between code, docs, and backlog workflows.

Quick Start

Audit active items in docs/bugs and docs/opportunities and align them with the current codebase, then archive completed work.

Frequently Asked Questions about backlog

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

FAQPage Schema
How do I reconcile bugs and opportunities with my current codebase?

Reconcile bugs and opportunities with your codebase by auditing active items in docs/bugs and docs/opportunities, aligning them with actual code changes, and archiving completed work to preserve traceability.

What is the best way to archive completed backlog items while preserving history?

Archiving completed backlog items involves moving resolved entries from active docs/bugs or docs/opportunities into their respective archive subfolders, which preserves historical data and maintains a clean, traceable project record.

How do I maintain consistent bug and opportunity tracking docs across a project?

Maintain consistent tracking docs by centralizing active items in docs/BUGS.md and docs/OPPORTUNITIES.md, enforcing canonical paths, and automatically updating these indexes whenever new items are filed or old ones are archived.

When should I triage my backlog of bugs and opportunities?

Triage your backlog of bugs and opportunities whenever you need to review outstanding items, verify their relevance against recent codebase updates, or file newly discovered issues to keep tracking docs aligned with reality.

Can I use backlog triage workflows to update canonical docs locations automatically?

Backlog triage workflows update canonical docs locations by enforcing specific archive rules and index updates for docs/BUGS.md and docs/OPPORTUNITIES.md whenever you review or reconcile active project items.