queue-prompt

Inspect git, CI, and thread state to resume or skip queued prompts.

12|2|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/osolmaz/tools --skill queue-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: queue-prompt
Source: https://github.com/osolmaz/tools/tree/main/agents/skills/queue-prompt
Command: npx skills add https://github.com/osolmaz/tools --skill queue-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and reconcile queued prompts, reminders, and retries to avoid duplicating work and ensure consistent progress on multi-step tasks.

Core Features & Use Cases

  • Detect queued or repeated instructions and treat them as potential duplicates rather than re-executing work.
  • Inspect state from source-of-truths (e.g., git, issues, PRs, artifacts, or conversation goals) to determine the correct unit of work and current status.
  • Continue unfinished work by building on the latest artifact instead of restarting, and skip operations that are already complete.

Quick Start

Prompt the AI to detect a queued prompt and decide whether to continue unfinished work or safely ignore duplicates.

Frequently Asked Questions about queue-prompt

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

FAQPage Schema
How do I avoid duplicating work when processing queued prompts and retries?

To avoid duplicating work with queued prompts, inspect truth sources like local repo state, git history, and CI results to classify work steps as done, in_progress, or blocked. This allows you to resume from the latest artifact without re-executing completed actions.

How does idempotent workflow automation handle repeated reminders and scheduled wakeups?

Idempotent workflow automation handles repeated reminders by identifying the concrete required outcome and determining whether to execute, continue, or skip. It inspects prior thread context and source-of-truths to safely ignore duplicate operations.

What is the best way to resume unfinished work from a previous CI run or git branch?

The best way to resume unfinished work is to inspect relevant truth sources such as git history and CI results to classify the current status. You then continue building on the latest artifact instead of restarting the entire task.

Can I use state inspection to skip operations on already completed issues and PRs?

Yes, you can use state inspection to skip operations on completed issues and PRs. By inspecting source-of-truths and classifying work steps as done or not_started, the system safely ignores duplicates and skips finished work.

Why does my prompt retry restart a multi-step task instead of continuing where it left off?

Prompt retries restart tasks because the system lacks state inspection to classify work steps as done, in_progress, or blocked. Inspecting prior thread context and truth sources prevents restarting and resumes from the latest artifact.

Do I need to manually check git history before processing repeated prompt instructions?

You do not need to manually check git history before processing repeated prompts. The system automatically inspects relevant truth sources including local repo state, git history, and CI results to determine if the work is already complete.