backlog

What it does

/cl-dev:backlog reviews the open issues in your project and helps you prioritize them. It looks across your backlog (the work that has been captured but not yet started), weighing each issue's clarity, scope, dependencies, and value, then applies a priority and a size to each one.

The result is an ordered, right-sized backlog you can pull from with confidence, rather than a flat pile of tickets.

When to use it

Reach for /cl-dev:backlog when your open issues have piled up and you need to decide what to work on next. It sits at the front of the workflow, before you commit to any single item:

• After a round of /cl-dev:spec has captured several new issues and you want to sort them.
• At the start of a planning session, sprint, or week, to re-rank what's open.
• Any time the backlog feels unordered and you're unsure which issue deserves attention first.

Once the backlog is prioritized, pick the top item and claim it with /cl-dev:claim-issue to begin work.

How to invoke it

Run it in your coding agent from a repository that's already set up for CodeLantern:

/cl-dev:backlog

No arguments are required. It works against the open issues in the project configured for the current repository. You can steer the pass in plain language (for example, ask it to focus on a particular area or theme), and it will walk you through the priorities before applying them.

Precondition: the repository must be initialized for CodeLantern (see /cl-dev:init) and connected to a project that has open issues to triage. If you're picking up existing work rather than sorting the backlog, use /cl-dev:set-context instead.