verne-orchestration

Orchestrate async Jules coding sessions across repositories via the Verne CLI.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/franklinbaldo/skills --skill verne-orchestration-franklinbaldo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verne-orchestration
Source: https://github.com/franklinbaldo/skills/tree/main/verne-orchestration
Command: npx skills add https://github.com/franklinbaldo/skills --skill verne-orchestration-franklinbaldo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delegating coding work to external Jules API sessions requires managing session creation, plan approvals, status monitoring, and multi-repository coordination, which is tedious to do manually through raw API calls. ## Core Features & Use Cases - Session Management: Create, list, inspect, and message Jules coding sessions on any repository using uvx verne commands with a JULES_API_KEY. - Plan Approval Workflow: Create sessions with required plan approval, review generated plans via session activities, and approve them before execution begins. - Multi-Repo Master/Worker Orchestration: Coordinate dependent worker sessions across repositories using a JSON orchestration schema with dependency tracking and heartbeat monitoring. - Use Case: After pushing a feature branch, launch an async review session with verne sessions create, monitor its state through QUEUED to COMPLETED, then iterate on the resulting PR by commenting, which automatically resumes Jules. ## Quick Start Ask the agent to create a Jules session on your repository with a prompt describing the coding task, then check its status with verne sessions list.

Frequently Asked Questions about verne-orchestration

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

FAQPage Schema
How do I create a Jules coding session from the command line?▼

Run verne sessions create with the target repository, branch, prompt, and title. Invoke Verne via uvx from the GitHub repository, so no permanent installation is needed, and set JULES_API_KEY first.

How do I approve a Jules plan before execution?▼

Create the session with the require-plan-approval flag, wait until the state reaches AWAITING_PLAN_APPROVAL, review the plan via verne sessions activities, then run verne sessions approve-plan with the session id.

When should I use Jules sessions instead of in-session subagents?▼

Use Jules sessions for async, cross-repository work that must persist after your current session ends. Use in-harness subagents for parallel LLM tasks like labeling or reviewing within the current session.

Why do Verne commands fail with a 401 error?▼

A 401 error means the JULES_API_KEY environment variable is missing or invalid. Obtain a key from the Jules settings page and export it before running any Verne command.

Can Jules resume work after I give feedback on a pull request?▼

Yes. Jules monitors PRs it created, and commenting with specific feedback moves the session to AWAITING_PLAN_APPROVAL. Approve the new plan to continue iterating instead of creating a new session.