Goal-Driven Queue

This skill owns the queue lifecycle: persistent backlog, intake-time approval capture, concurrent consumption, queue-level caps, progress document, acceptance package, and the post-run human per-card verification gate. Single-run methodology lives in goal-driven-workflow (the engine); merge decisions stay human. Loading this skill MUST NOT start consumption by itself — consumption starts only on an explicit queue request or a scheduled pull. References stay thin: evolution-review (kill vocabulary, record-the-failed-recipe), learn-and-improve (carrier decision tree) and solution-review (reversibility / CBAM / WSJF vocabulary) supply vocabulary only and are deliberately not frontmatter dependencies — their absence degrades a recommendation's richness, never a gate.

The value proposition is the detach-run-accept cycle: a human drops approved goals into the backlog during spare moments, leaves, and returns later to a packaged result. Every design choice below serves that promise — nothing may stall waiting for an absent human, and nothing may proceed past what the human actually approved.

Prerequisite Skill Check

Run at startup against frontmatter dependencies: scan available skills; abort immediately with install guidance (npx skills add FuDesign2008/open-skills -g) if report-output-discipline, goal-driven-workflow, design-approval-gate, or intake-interview-discipline is missing; abort likewise for ai-proxy-discipline when any card records Stage-exit policy: ai-proxy, for jira-fix-workflow / opsx-jira-fix-workflow when any card names them as Engine, and for git-worktree-discipline when the queue's resolved concurrency is ≥ 2 (missing at concurrency 1 is not a failure); missing with no such card or concurrency is not a failure. No silent downgrade — a missing engine means queued tasks cannot execute correctly; a missing intake discipline means enqueue-time depth collapses to a shallow one-shot confirm; a missing proxy discipline means opted-in cards lose their checkpoint challenge; a missing worktree discipline means concurrent children would lose their isolation.

Queue Layout