Schedule (Jules Dispatch)

Dispatch planned ledger items to Jules and hand off tracking to heartbeat.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill schedule-jules-dispatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Schedule (Jules Dispatch)
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/schedule
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill schedule-jules-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Schedule this skill to automate dispatch of planned work-ledger items to Jules, mark them active, and hand off tracking to heartbeat PR polling.

Core Features & Use Cases

  • Validate item existence and eligibility in the ledger (default: status is planned or pending; force override available)
  • Dispatch with Jules session creation, ledger updates, and orchestration metadata
  • Integrate with heartbeat to monitor PR status and update ledger accordingly
  • Maintain traceability with session links, repo targets, and run IDs

Quick Start

Dispatch a planned ledger item by specifying the item_id and mode, then monitor the resulting Jules session.

Frequently Asked Questions about Schedule (Jules Dispatch)

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

FAQPage Schema
How do I automate dispatching planned work items to Jules from a ledger?

To automate Jules dispatch, you schedule the skill to validate planned ledger items, create Jules sessions, update orchestration metadata, and hand off tracking to heartbeat PR polling.

Can I force a re-dispatch of a pending work item to Jules if it already exists?

Yes, you can re-dispatch pending ledger items to Jules by specifying a force override mode, which bypasses default status eligibility checks and triggers a new session creation.

How does heartbeat tracking monitor the status of dispatched Jules work items?

Heartbeat tracking monitors dispatched Jules work items by polling PR status, updating the ledger accordingly, and maintaining traceability through session links, repo targets, and run IDs.

What ledger statuses are eligible for dispatching work items to Jules?

Default eligible ledger statuses for dispatching to Jules are planned or pending; the system enforces these status mappings and requires item existence before proceeding with session creation.

Do I need to manually update ledger links after dispatching a work item to Jules?

No, the dispatch automation updates ledger links and orchestration fields automatically after creating the Jules session, ensuring traceability without requiring manual metadata entry.

Why does my Jules dispatch workflow fail when the ledger item status is invalid?

Jules dispatch fails for invalid statuses because the workflow enforces ledger status mappings, requiring items to be planned or pending unless explicitly overridden with a force mode.