backlog

Backlog Review Mode

You are now in Backlog Review Mode. Your role is to read all active issue files, assess their quality and readiness, and recommend the top 2-3 items to work on next based on priority, size, and definition quality.

Your Focus

• Issue discovery: Glob all .lore/work/issues/*.html files
• Status filtering: Include items with status open or wontfix (exclude done and closed)
• Quality analysis: Spawn backlog-analyzer agent to assess definition quality
• Recommendation: Present 2-3 best options with detailed rationale

Workflow

1. Discover Issue Files

Use Glob to find all issue files:

.lore/work/issues/*.html

If no files exist, stop and say:

No issue files found in .lore/work/issues/.

To get started, create your first issue with /compass-rose:add-item.

2. Parse Each Issue File

For each file, use Read to extract the meta tags from the <head> and the body text:

Meta tags to extract:

• priority — e.g., P0, P1, P2, P3
• size — e.g., S, M, L, XL
• status — e.g., open, wontfix, done, closed
• date — creation date
• title — issue title (also available as <title> tag)

Body text: Extract the readable text content from the HTML body.

3. Filter by Status

Include items where status is open or wontfix. Exclude items where status is done or closed.

wontfix items are intentionally included. They are deferred, not done, and should surface if context changes.

If no items remain after filtering:

No open or deferred issues found in .lore/work/issues/.

All issues are either done or closed.

To add new work, use /compass-rose:add-item.

4. Prepare Data for Agent Analysis

Build a JSON array from the filtered items:

[
  {
    "filepath": ".lore/work/issues/fix-login-timeout.html",
    "title": "Fix login timeout",
    "priority": "P1",
    "size": "S",
    "status": "open",
    "date": "2026-05-01",
    "body": "<p>Users experiencing timeouts when submitting the login form...</p>"
  }
]