backlog-feature-improvementlisted

Audit the stapler-squad backlog automation/reconciliation feature — current item state, the UI, and the code — using ux:review, quality:architecture-review, code:review, and code:is-it-ready, to find gaps blocking the goal of a fully autonomous, user-configurable end-to-end delivery pipeline (e.g. letting a user pick which skills, like their SDD skills, run per item) — then routes each finding through the matching SDD entry point (sdd:fix-bug / sdd:quick / sdd:full) to research, plan, and implement the fix. Use for periodic health checks, when items report stuck/silently-failing, or when asked how to get closer to a "software factory."
tstapler/stapler-squad · ★ 1 · AI & Automation · score 64

Install: claude install-skill tstapler/stapler-squad

# Backlog Feature Improvement The backlog feature's end goal: an item goes idea → shipped PR with minimal human intervention, and the pipeline stages (triage → plan → implement → review → merge) are configurable per item — a user can say "use `/sdd:full` for this one" or "skip review gate for this one." Today the pipeline is fixed and hardcoded (see Known Findings below). This skill audits state, UI, and code against that goal and produces a prioritized gap list. ## Before You Start — Check Prior Art Many investigations already exist. Skim before re-deriving: - `project_plans/backlog-stuck-item-visibility/` — root causes: auto-merge disabled, silent rework cap, non-durable notify-once state - `project_plans/backlog-triage-autonomous/`, `backlog-triage-e2e-hardening/`, `backlog-service-refactor/`, `backlog-ux/`, `backlog-pr-conflict-detection/`, `backlog-cross-platform-audit/`, `backlog-management/` - `docs/adr/ADR-022-headless-triage-over-autonomous-driver.md` — why triage is a direct headless pool call (`pool.CallBlockingWithOptions`), not a tmux-driven `AutonomousDriver` - `docs/adr/013-workflow-engine-replaces-valid-transitions.md` — `session/workflow_engine.go` is the intended seam for custom/configurable states (S2/S3 in that ADR); check whether it's wired up yet or still just replacing the static map ## Known Findings (2026-07-14 hotspot scan — verify still true before reporting as new) **Reconciliation-loop hotspots** (churn × complexity), highest risk first: - `