lintel-board-prioritise

/lintel-board-prioritise — Groom and Prioritise Board Work Items

Review all work items on the board, clean up completed/stale items, break down oversized tasks, and prioritise the backlog aligned with the Lintel vision.

Context: Lintel Vision

Lintel is the AI-human engineering platform — both measurement system and execution engine. Prioritisation should favour work that advances these pillars (in order):

1. Event infrastructure — event store, bus, projections, subscriptions
2. Collaboration & routing — teams, channels, integrations
3. Guardrails & safety — cost limits, escalation, sandbox hardening
4. Deployment & observability — deployments, incidents, feature flags
5. Measurement & analytics — DORA metrics, agent accuracy, team velocity
6. Continuous improvement — learning loops, automated remediation

Workflow Capacity Reference

A single feature_to_pr workflow run can handle work that fits in roughly one focused feature or bug fix — 11 stages: ingest → route → setup_workspace → research → plan → implement (up to 5 review cycles) → review → close. If a task requires multiple unrelated code changes across different packages, or touches more than ~3 files substantially, it should be broken down.

Steps

1. Fetch current state

Use MCP tools to gather data:

• mcp__lintel__boards_list_boards — get all boards (needs a project_id; list projects first if needed)
• mcp__lintel__work-items_list_work_items — get all work items

Present a summary table of current work items grouped by status.

2. Groom — remove completed work

Identify work items with terminal statuses (merged, closed) — these are done. Delete them with mcp__lintel__work-items_remove_work_item.

Also identify failed items — ask the user whether to retry (move back to open) or delete.

Report what was cleaned up.

3. Assess scope — break down oversized tasks

For each remaining open work item, evaluate whether it can be completed in a single feature_to_pr run: