Prompt-pack worker

Feature FW-WC-009. Workcell prompt_pack_worker.

Updated

Who this is for

Operators on this laptop who want a zip of markdown prompts implemented in Cursor, then an optional allowlisted deploy, supervised from Element #cursor-plain.

Problem

A freeform prompt pack still needs a human gate before a write-capable agent runs, and a second gate before anything is deployed.

What you can do

  • Upload a .zip with the caption !agent pack.
  • Reply approve or reject on the acknowledgement.
  • After IMPLEMENTED or FAILED, read AUDIT.
  • Reply deploy only when you want the allowlisted commands in the frozen plan.
  • Use the follow-ups already defined for the same pack: testplan, acceptance, test, dual-wiki, fix, catchup, commit, push.

What you cannot do

  • Start this on Granite with !agent task. That is the agentic-dev worker.
  • Deploy before IMPLEMENTED, or run a command that is not on the allowlist.
  • Queue a second pack while one is still active.

Limits

Model is Grok 4.7 only. The zip is markdown and text, at most 20 MB and 200 files. Cursor gets at most three implement turns, then the run fails closed with the unfinished list. IMPLEMENTED means the completion scan passed.

Next

System page · Prompt-pack protocol