goal-prompt-dispatch

Executes one queued GOAL prompt file per run from a four-folder filesystem queue.

Updated May 20, 2026
One-click install
npx skills add https://github.com/TeXmeijin/agent-skills --skill goal-prompt-dispatch-texmeijin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goal-prompt-dispatch
Source: https://github.com/TeXmeijin/agent-skills/tree/main/.apm/skills/goal-prompt-dispatch
Command: npx skills add https://github.com/TeXmeijin/agent-skills --skill goal-prompt-dispatch-texmeijin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It lets you batch high-quality GOAL prompts in a queue and have a fresh, memoryless agent session execute them later, one at a time, without double-processing or losing track of completed and failed work. ## Core Features & Use Cases - Single-item dispatch: Picks the oldest GOAL file from ~/.goal-prompt-queue/inbox/ by created_at and atomically moves it to inprogress/ so concurrent runners never grab the same task. - Four-folder lifecycle: Tracks every GOAL through inbox → inprogress → done/error, appending completed_at and a result summary to the file's frontmatter. - Memoryless autonomous execution: Reads workspace_directory from frontmatter, changes into that project, and executes the GOAL body via /goal or as a direct task brief, honoring CONSTRAINTS, DONE WHEN, VERIFY, and STOP RULES. - Use Case: Schedule a cron job that invokes this skill nightly so queued GOALs prepared during the day are executed unattended by Claude or Codex, with PRs created and results recorded by morning. ## Quick Start Run the goal-prompt-dispatch skill to pick up and execute the oldest GOAL waiting in my queue.

Frequently Asked Questions about goal-prompt-dispatch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run queued GOAL prompts automatically on a schedule?

Invoke this skill from a cron job or scheduled task with a prompt that calls /goal-prompt-dispatch. Each launch processes at most one GOAL file from ~/.goal-prompt-queue/inbox/, so schedule recurring triggers to drain the queue over time.

How does the queue prevent two runners from executing the same task?

The runner selects the oldest inbox file by created_at and immediately moves it to inprogress/ with mv, which is atomic on the same filesystem. A second runner attempting the same file fails because the source no longer exists and exits without picking another.

Can I use this dispatch runner with both Claude and Codex?

Yes, the queue lives at ~/.goal-prompt-queue/ in the home directory so both Claude and Codex sessions point at the same files. The runner adapts subagent model tiers to whichever platform executes it, such as Sonnet for Claude.

What happens when GitHub authentication expires during execution?

The runner stops at local branch and commit state without pushing, records the situation in the result field, and moves the file to error/ or done/ depending on the GOAL's STOP RULES. It also leaves a PR title and body draft for later pickup.

What are the limitations of this dispatch approach?

It processes only one GOAL per launch and never recovers files stuck in inprogress/ after a crash; a human must move those back to inbox/ or error/. It also assumes each GOAL file is fully self-contained since the runner starts with zero conversation memory.