Feature Request: Backlog and Iterative Spec Roadmapping capability #56

Problem
We need a lightweight way to (1) separate “not ready” work from “ready to build” work, and (2) continuously review specs to determine maturity and rollout intent so the autocoder can prioritize correctly. Today, items that are underspecified or blocked can mix with build-ready tasks, and spec maturity is not encoded in a way the agent can act on.

Goal
Add two connected capabilities:

• A clear Backlog state for uncommitted / not-ready work.
• An Iterative Spec Roadmapping workflow that assigns maturity tags (alpha, limited beta, beta) which directly influence the autocoder’s prioritization.

1) Backlog State (Not Committed / Not Ready)

Definition
Backlog = not committed / not ready (may be missing requirements, acceptance criteria, dependencies, or decision-maker input).
Behavior
Items in Backlog are excluded from the autocoder’s build queue by default.
A work item can only be promoted out of Backlog when it meets “ready” checks (see Pending below).

2) Iterative Spec Roadmapping (Spec Review + Maturity Tags)

Concept
A repeatable spec-review action that assigns a maturity tag to each work item:
alpha: early/experimental; may ship behind flag; minimal scope; higher tolerance for iteration.
limited beta: scoped rollout to a subset of users/workspaces; tighter acceptance criteria; explicit guardrails.
beta: broader readiness; stronger quality bar; stable requirements.

Workflow
Add a “Spec Review” step (manual or semi-automated) that results in:
A required maturity tag: alpha / limited beta / beta
Optional notes: rollout constraints, risks, must-not-break areas, dependencies.

Autocoder Prioritization
Autocoder sorts work primarily by:
Column eligibility (only Pending is build-ready)
Maturity tag priority (configurable default, e.g. beta > limited beta > alpha)
Secondary signals (impact, due date, dependencies resolved, etc.)

Board Semantics (Must Match System Behavior)
Backlog = not committed / not ready
Pending = fully specified + unblocked + acceptable criteria/tests defined
In Progress = agent is actively executing
Review / QA = PR open + checks running + human approval needed
Done = merged + checks green (+ deployed if that’s your definition)

Guardrail
Autocoder may only start work from Pending (never from Backlog).

Acceptance Criteria
Work items can be tagged alpha / limited beta / beta from the UI and via API.
The maturity tag is visible on cards and filterable.
Autocoder prioritizes build-ready work based on the maturity tag (with configurable ordering).
“Ready checks” are enforced for moving items into Pending (or at minimum strongly warned).
Backlog items are excluded from the agent queue unless explicitly overridden by a human.

Nice-to-have
Dashboard showing counts by maturity tag and stage (e.g., Pending-beta, Pending-alpha).
A “Spec completeness” checklist that drives promotion from Backlog → Pending.