async-invoke

Dispatch background agents with structured manifests and track status via SCRATCHPAD.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/reiserwang/Coding_Agent --skill async-invoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: async-invoke
Source: https://github.com/reiserwang/Coding_Agent/tree/main/.gemini/skills/async-invoke
Command: npx skills add https://github.com/reiserwang/Coding_Agent --skill async-invoke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch one or more agents as background jobs with structured manifests and track their status via SCRATCHPAD. This approach lets tasks run independently while the main agent continues, ensuring deterministic state and progress visibility.

Core Features & Use Cases

  • Launch and monitor background agents as separate jobs using a manifest-driven protocol.
  • Track status in SCRATCHPAD and update a centralized ASYNC_JOBS table for real-time visibility.
  • Collect results, post to Handoff Queue, and trigger downstream workflow across Gemini and Claude Code runtimes.

Quick Start

Create manifests for each job in workspace/state/async-jobs and dispatch them with async-invoke:dispatch to run as background tasks.

Frequently Asked Questions about async-invoke

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

FAQPage Schema
How do I run background agents in parallel with Gemini and Claude Code?

To run background agents in parallel, you can dispatch independent tasks concurrently on Gemini using nohup and Claude Code using the Task tool, tracking their progress through a structured manifest and SCRATCHPAD.

What is a manifest-driven workflow for orchestrating background agents?

A manifest-driven workflow for background agents uses a structured JSON file to define job parameters, allowing you to dispatch tasks independently while maintaining deterministic state and real-time progress visibility via SCRATCHPAD.

How do I track the status of background jobs dispatched to Claude Code or Gemini?

You track the status of dispatched background jobs by updating a centralized ASYNC_JOBS table and using specific status commands to monitor the SCRATCHPAD, ensuring real-time visibility of concurrent tasks.

Can I collect results from concurrent background agents and trigger downstream workflows?

Yes, you can collect results from concurrent background agents, post them to a Handoff Queue, and trigger downstream workflows across Gemini and Claude Code runtimes after the parallel tasks complete.

What do I need to set up before dispatching background agents as separate jobs?

Before dispatching background agents, you need to create a manifest JSON file under a specific workspace state directory for async jobs, which structures the job parameters for the concurrent runtimes.

Why use structured manifests instead of standard background tasks for parallel agents?

Structured manifests ensure deterministic state and progress visibility for parallel agents, allowing independent tasks to run concurrently across different runtimes while the main agent continues working without interruption.