overlord-cli 5.3.0 → 5.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord-cli",
-  "version": "5.3.0",
+  "version": "5.4.0",
   "description": "Overlord CLI — launch AI agents on tickets from anywhere",
   "type": "module",
   "bin": {

package/plugins/claude/skills/overlord-ticket/SKILL.md

@@ -127,6 +127,15 @@ ovld protocol discover-project
 
 You can override with `--project-id` or `--working-directory` if needed.
 
+### Choosing `--execution-target`
+
+Pass `--execution-target agent` or `--execution-target human` (default: `human`) when creating tickets.
+
+- **`agent`** — any task an AI agent can complete in a computer environment: coding, internet research, document editing, data analysis, automated testing, etc.
+- **`human`** — any task requiring human presence or judgment: setting credentials or tokens in a third-party UI (e.g. Vercel, AWS), sending physical mail, making a product or business decision, physical-world actions.
+
+When in doubt, ask yourself: *can this be done entirely inside a terminal or browser by an AI without human intervention?* If yes → `agent`. If it requires a human to log in, decide, or act in the real world → `human`.
+
 ## Context And Artifacts
 
 ```bash
@@ -145,3 +154,5 @@ ovld protocol artifact-download-url --session-key <sessionKey> --ticket-id $TICK
 - Use `write-context` for facts a future agent session should know.
 - Do not add or commit changes unless the user explicitly asks you to commit.
 - Delivery is the concluding step. After delivering, stop unless the user follows up or the ticket is reopened.
+
+<!-- version: 0.2.2 -->

package/plugins/cursor/skills/overlord-ticket/SKILL.md

@@ -27,9 +27,21 @@ Use this skill whenever Cursor needs to work with Overlord, whether the session
 6. If you need other lifecycle commands or flags, run `ovld protocol help` and use the real subcommand list instead of guessing.
 7. Once you attach to a ticket, switch back to Mode 1 and follow the full ticket lifecycle.
 
+## Choosing `--execution-target` When Creating Tickets
+
+Pass `--execution-target agent` or `--execution-target human` (default: `human`) when creating tickets.
+
+- **`agent`** — any task an AI agent can complete in a computer environment: coding, internet research, document editing, data analysis, automated testing, etc.
+- **`human`** — any task requiring human presence or judgment: setting credentials or tokens in a third-party UI (e.g. Vercel, AWS), sending physical mail, making a product or business decision, physical-world actions.
+
+When in doubt, ask yourself: *can this be done entirely inside a terminal or browser by an AI without human intervention?* If yes → `agent`. If it requires a human to log in, decide, or act in the real world → `human`.
+
 ## Rules
 
 - Always attach first and always deliver last once you are on a ticket.
 - Use `ovld protocol` commands, the plugin commands, and the MCP tool instead of ad hoc scripts.
 - Do not invent protocol subcommands. Use `ovld protocol help` when unsure.
 - Include at least one progress update before delivering.
+- When creating follow-up tickets, always set `--execution-target` explicitly using the `agent`/`human` rule above.
+
+<!-- version: 0.2.2 -->

package/plugins/overlord/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Chat-driven access to Overlord ticket protocol workflows.",
   "author": {
     "name": "Cooperativ",
@@ -23,9 +23,9 @@
     "privacyPolicyURL": "https://www.ovld.ai/privacy",
     "termsOfServiceURL": "https://www.ovld.ai/terms",
     "defaultPrompt": [
-      "Attach to Overlord ticket 123 and summarize the context before editing code",
-      "Post an execute update to this Overlord ticket after a meaningful implementation step",
-      "Deliver this Overlord ticket with artifacts and change rationales"
+      "Create an Overlord ticket with the objective 'Implement feature X' and summarize the context before editing code",
+      "Execute Overlord ticket [ticket-id]",
+      "Find all Overlord tickets with the status 'next-up' and prioritize the most important one"
     ],
     "brandColor": "#1E6B5C",
     "composerIcon": "./assets/icon.png",

package/plugins/overlord/skills/overlord-ticket/SKILL.md

@@ -121,6 +121,15 @@ ovld protocol create --agent codex --objective "Capture follow-up work from this
 ovld protocol spawn --agent codex --objective "Implement feature X" --priority medium
 ```
 
+### Choosing `--execution-target`
+
+Pass `--execution-target agent` or `--execution-target human` (default: `human`) when creating tickets.
+
+- **`agent`** — any task an AI agent can complete in a computer environment: coding, internet research, document editing, data analysis, automated testing, etc.
+- **`human`** — any task requiring human presence or judgment: setting credentials or tokens in a third-party UI (e.g. Vercel, AWS), sending physical mail, making a product or business decision, physical-world actions.
+
+When in doubt, ask yourself: *can this be done entirely inside a terminal or browser by an AI without human intervention?* If yes → `agent`. If it requires a human to log in, decide, or act in the real world → `human`.
+
 ## Rules
 
 - The authoritative lifecycle is the `ovld protocol` CLI once you are on a ticket.
@@ -128,3 +137,5 @@ ovld protocol spawn --agent codex --objective "Implement feature X" --priority m
 - Prefer the installed `ovld` CLI and the plugin's MCP tools instead of ad hoc repo scripts.
 - Do not create or rely on a local Codex `AGENTS.md` bundle for Overlord.
 - When the ticket was launched by Overlord, the ticket prompt remains authoritative for the specific task objective and ticket-level constraints.
+
+<!-- version: 0.2.2 -->