yellow-jules

Plugin yellow-jules from marketplace yellow-plugins in KingInYellows/yellow-plugins. Commands read from the repo's manifest — today.

Skills (2)

• jules-delegation

  Host-neutral reference for delegating work to Google Jules through the yellow-jules CLI: the session lifecycle, the one-JSON-object CLI contract, the grant every write needs, and how to recover from an unknown outcome. Use when building or reasoning about a surface that sends work to Jules.

• jules-supervision

  Host-neutral reference for supervising a Google Jules session with one bounded pass at a time: the decision table, what each decision allows, pause handling, and the correction limits. Use when you are asked to keep a Jules session moving inside a grant, or to read what a session needs next.

Slash commands (10)

• /yellow-jules:jules:abandon

  Prepare the terminal command that abandons a Google Jules launch or message whose outcome could not be determined, freeing its repository and branch guard. Use when status --reconcile left an operation ambiguous or not-reached and the user decides to give it up.

• /yellow-jules:jules:approve

  Approve the pending plan of a Google Jules session under an owner-written grant, after re-reading the plan fresh from the vendor and confirming with the user. Use when the user wants to approve a Jules plan or let a session start executing.

• /yellow-jules:jules:authorize

  List or revoke Google Jules grants, or prepare the terminal command that writes a new grant or moves the controller to this host. Use when the user wants to see what Jules may do unattended, revoke a grant, or authorize Jules to work on a branch.

• /yellow-jules:jules:collect

  Stage a Google Jules session's patches, generated files, and pull-request references into the yellow-jules data directory for local review, without touching any checkout. Use when the user wants to fetch, download, or inspect what a Jules session produced.

• /yellow-jules:jules:delegate

  Launch a Google Jules session on a repository branch under an owner-written grant, always dry-run validated and user-confirmed before anything is sent. Use when the user says to have Jules do a task, send a task to Jules, or delegate work to Jules.

• /yellow-jules:jules:list

  List one page of Google Jules sessions with their normalized condition, matched against the local journal. Use when the user asks what Jules sessions exist, wants a session id for /jules:status or /jules:collect, or wants to page through Jules sessions.

• /yellow-jules:jules:reply

  Send one message to a Google Jules session under an owner-written grant, dry-run validated and user-confirmed first. Use when the user wants to answer a Jules question, give a session feedback, or request a correction.

• /yellow-jules:jules:setup

  Check Jules credential and SDK availability and, with consent, install the pinned Jules SDK into the plugin data directory. Use when first installing yellow-jules, after JULES_API_KEY changes, or when a jules command fails with JULES_SDK_MISSING or JULES_SDK_INTEGRITY.

• /yellow-jules:jules:status

  Check the live state of one Google Jules session — normalized condition, new activities, pending plan, and outputs — reading fresh from the vendor. Use when the user asks how a Jules session is doing, whether it is waiting on plan approval or a reply, or what it produced.

• /yellow-jules:jules:supervise

  Run one bounded supervision pass over a Google Jules session under a grant, then act on its decision with at most one reply or approval. Use when the user wants Jules supervised, asks what a session needs next, or wants a plan reviewed or a question answered inside the grant's limits.

Similar plugins