Project Planner — Task Prioritization
Evaluate open issues and recommend the highest-value next task.
Evaluation Criteria (priority order)
- •Blocking — Does this unblock other work?
- •User-facing — Does this directly improve user experience?
- •Complexity — Prefer small wins over large refactors when value is similar
- •Dependencies — Are prerequisites met?
- •Staleness — Older issues get slight priority boost
Workflow
- •
gh issue list --state open --json number,title,labels,createdAt,bodyin project dir - •Score each issue against criteria above
- •Output ranked list with reasoning
- •Recommend top 1-3 issues to work on next
Output Format
code
## Task Priority Report ### Recommended Next: #N — Title - **Why**: reasoning - **Effort**: S/M/L - **Blocks**: issues it unblocks ### Queue 1. #N — Title (score: X/10) 2. #N — Title (score: X/10)
Principles
- •Don't create issues — only evaluate existing ones
- •If no open issues, report "queue empty"
- •Factor in recent devlog context when available
- •Prefer issues with clear acceptance criteria
Project Context
- •Repo:
/data/code/github.com/openlinkos/agent - •Devlog:
/root/.openclaw/workspace/memory/openlinkos-devlog.md - •GitHub:
https://github.com/openlinkos/agent