odd-studio 3.3.4 → 3.3.6

package/README.md

@@ -45,9 +45,15 @@ npx odd-studio init my-project --agent codex
 cd my-project
 ```
 
-In Codex, start ODD by saying `use ODD` or `start ODD`.
-Codex reads `AGENTS.md`, which routes the session to `plugins/odd-studio/skills/odd/SKILL.md`.
-Once ODD is active, the same starred flow works there too, including commands like `*plan`, `*build`, and `*status`.
+In Codex, start ODD with `/odd`.
+Use `/odd-status` when you want the current project state without entering the full planning or build flow.
+`AGENTS.md` remains supporting context, but the Codex plugin command is the primary entrypoint.
+
+If this project was originally set up for Claude Code or OpenCode and you want to add Codex later, run:
+
+```bash
+npx odd-studio upgrade --agent codex
+```
 
 ### For Claude Code and OpenCode on the same machine
 
@@ -77,7 +83,7 @@ That single command:
 **Then open your project in your AI coding agent and start ODD:**
 ```
 Claude Code / OpenCode: /odd
-Codex: use ODD
+Codex: /odd
 ```
 
 ---
@@ -88,7 +94,7 @@ Codex: use ODD
 |-------|-------------------|---------------|
 | **Claude Code** | Project-local skills (`.claude/skills/`), hooks (`.claude/settings.local.json`), odd-flow MCP (`.mcp.json`) | Claude (Opus, Sonnet, Haiku) |
 | **OpenCode** | Project-local commands (`.opencode/commands/`), JS plugin (`.opencode/plugins/`), odd-flow MCP (`opencode.json`) | Any provider — Ollama (Qwen3-Coder, MiniMax M2.7, DeepSeek), OpenAI, Anthropic, Google, Groq, and 75+ more |
-| **Codex** | Project-local plugin (`plugins/odd-studio/`), local marketplace registration (`.agents/plugins/marketplace.json`), plugin MCP (`plugins/odd-studio/.mcp.json`) | Codex |
+| **Codex** | Project-local plugin (`plugins/odd-studio/`), slash-command entrypoints (`plugins/odd-studio/commands/`), local marketplace registration (`.agents/plugins/marketplace.json`), plugin MCP (`plugins/odd-studio/.mcp.json`) | Codex |
 
 All supported agents get the same methodology, the same safety enforcement, and the same odd-flow-powered cross-session memory. The only difference is the delivery mechanism.
 
@@ -101,7 +107,7 @@ Your AI coding agent loads the ODD orchestrator. It checks whether you have an e
 - **New project:** Welcomes you, explains what you're about to build together, and starts with the first question: *Who uses this system, and what do they actually need?*
 - **Returning project:** Shows you exactly where you left off and resumes from there. Nothing is lost between sessions.
 
-From there, use the dedicated direct commands listed below in Claude Code or OpenCode, or type sub-commands inside the active ODD session.
+From there, use the dedicated direct commands listed below in Claude Code, OpenCode, or Codex, or type sub-commands inside the active ODD session.
 
 ---
 
@@ -158,8 +164,7 @@ ODD Studio installs safety gates that run automatically throughout your build. T
 
 **Claude Code:** Implemented as shell hooks registered in `.claude/settings.local.json` (project-local).
 **OpenCode:** Implemented as a JS plugin (`odd-studio-plugin.js`) in `.opencode/plugins/` (project-local).
-**Codex:** Implemented as a project-local plugin in `plugins/odd-studio/` with `hooks.json` and plugin-local skills.
-Codex starts through `AGENTS.md` instructions (`use ODD` / `start ODD`) rather than a guaranteed `/odd` composer command.
+**Codex:** Implemented as a project-local plugin in `plugins/odd-studio/` with `hooks.json`, plugin-local skills, and slash commands such as `/odd` and `/odd-status`.
 
 ---
 

package/bin/commands/init.js

@@ -218,7 +218,7 @@ function printNextSteps({ isClaude, isOpenCode, isCodex, projectName }) {
   }
   if (isCodex) {
     console.log(`  ${stepN++}. Open your project in Codex`);
-    console.log(`  ${stepN++}. Start ODD by saying: ` + chalk.cyan('use ODD') + chalk.dim(' (Codex reads AGENTS.md automatically — no /odd command needed)'));
+    console.log(`  ${stepN++}. Start ODD in Codex: ` + chalk.cyan('/odd') + chalk.dim(' (use /odd-status to inspect state first)'));
   }
   if (isClaude || isOpenCode) {
     console.log(`  ${stepN++}. Start your ODD session: ` + chalk.cyan('/odd'));

package/bin/commands/status.js

@@ -43,7 +43,7 @@ export function registerStatus(program, deps) {
       }
 
       print.blank();
-      console.log(chalk.dim('  Open your AI coding agent and type /odd to resume.'));
+      console.log(chalk.dim('  Open your AI coding agent and type /odd to resume. Use /odd-status for a state-only check.'));
       print.blank();
     });
 }

package/bin/odd-studio.js

@@ -15,7 +15,7 @@ import { registerUninstall } from './commands/uninstall.js';
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
 const require = createRequire(import.meta.url);
-const pkg = require('../package.json'); // v3.3.4
+const pkg = require('../package.json'); // v3.3.6
 
 const PACKAGE_ROOT = path.resolve(__dirname, '..');
 const deps = { PACKAGE_ROOT, print };

package/codex-plugin/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "odd-studio",
-  "version": "3.3.3",
+  "version": "3.3.6",
   "description": "Outcome-Driven Development planning and build harness for domain experts building serious software with AI.",
   "author": {
     "name": "ODD Studio"
@@ -21,7 +21,7 @@
   "interface": {
     "displayName": "ODD Studio",
     "shortDescription": "Guide planning, build sequencing, and verification with Outcome-Driven Development",
-    "longDescription": "Use ODD Studio to plan around personas, outcomes, contracts, and phased delivery, then run a disciplined build and verification flow with odd-flow memory and safety gates.",
+    "longDescription": "Use ODD Studio to plan around personas, outcomes, contracts, and phased delivery, then run a disciplined build and verification flow with odd-flow memory, safety gates, and Codex slash commands such as /odd and /odd-status.",
     "developerName": "ODD Studio",
     "category": "Coding",
     "capabilities": [
@@ -32,7 +32,7 @@
     "websiteURL": "https://github.com/odd-studio/odd-studio",
     "privacyPolicyURL": "https://github.com/odd-studio/odd-studio",
     "termsOfServiceURL": "https://github.com/odd-studio/odd-studio",
-    "defaultPrompt": "Start or resume an ODD Studio planning and build session for this project",
+    "defaultPrompt": "Run /odd to start or resume this ODD Studio project, or /odd-status to inspect the current state",
     "brandColor": "#111111",
     "screenshots": []
   }

package/codex-plugin/README.md

@@ -1,3 +1,6 @@
 # ODD Studio for Codex
 
 This plugin installs the ODD Studio planning and build harness into Codex as a project-local plugin.
+
+Primary entrypoints in Codex are `/odd` to start or resume and `/odd-status` to inspect the current project state.
+`AGENTS.md` can reinforce the workflow, but the plugin command is the canonical startup path.

package/hooks/odd-studio.sh

@@ -184,13 +184,30 @@ verify-gate)
   # Only intercept writes to state.json
   echo "$FILE_PATH" | grep -q 'state\.json' || exit 0
 
-  # Check if the write is setting buildStatus to "verified"
-  NEW_CONTENT=$(echo "$INPUT" | jq -r '.tool_input.new_string // .tool_input.content // empty')
-  echo "$NEW_CONTENT" | grep -q '"verified"' || exit 0
+  # Count verified statuses: only block if NEW outcomes are being marked verified
+  # (not when existing verified outcomes are preserved in a full file write)
+  if [ "$TOOL_NAME" = "Write" ]; then
+    # Full file write — compare verified count against existing file
+    NEW_CONTENT=$(echo "$INPUT" | jq -r '.tool_input.content // empty')
+    NEW_VERIFIED=$(echo "$NEW_CONTENT" | grep -c '"buildStatus"[[:space:]]*:[[:space:]]*"verified"' || echo 0)
+    if [ -f "$FILE_PATH" ]; then
+      OLD_VERIFIED=$(grep -c '"buildStatus"[[:space:]]*:[[:space:]]*"verified"' "$FILE_PATH" || echo 0)
+    else
+      OLD_VERIFIED=0
+    fi
+    [ "$NEW_VERIFIED" -gt "$OLD_VERIFIED" ] || exit 0
+  else
+    # Edit — check if new_string introduces "verified" that old_string didn't have
+    OLD_STRING=$(echo "$INPUT" | jq -r '.tool_input.old_string // empty')
+    NEW_STRING=$(echo "$INPUT" | jq -r '.tool_input.new_string // empty')
+    OLD_HAS=$(echo "$OLD_STRING" | grep -c '"verified"' || echo 0)
+    NEW_HAS=$(echo "$NEW_STRING" | grep -c '"verified"' || echo 0)
+    [ "$NEW_HAS" -gt "$OLD_HAS" ] || exit 0
+  fi
 
   VERIFIED_CONFIRMED=$(get_state_field "verificationConfirmed")
   if [ "$VERIFIED_CONFIRMED" != "true" ]; then
-    echo "ODD STUDIO [verify-gate]: Cannot mark outcomes as verified." >&2
+    echo "ODD STUDIO [verify-gate]: Cannot mark NEW outcomes as verified." >&2
     echo "Walk through the verification checklist first. Set verificationConfirmed: true after all steps pass." >&2
     exit 2
   fi

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "odd-studio",
-  "version": "3.3.4",
+  "version": "3.3.6",
   "description": "Outcome-Driven Development for AI coding agents — a planning and build harness for domain experts building serious software with AI. Works with Claude Code, OpenCode, and Codex.",
   "keywords": [
     "claude-code",

package/skill/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "odd"
-version: "3.3.4"
+version: "3.3.6"
 description: "Outcome-Driven Development planning and build coach. Use /odd to start or resume an ODD project — building personas, writing outcomes, mapping contracts, creating a Master Implementation Plan, and directing a odd-flow-powered build. Designed for domain experts who are not developers. Works with Claude Code, OpenCode, and Codex."
 ---
 
@@ -35,7 +35,7 @@ Display this when no existing state is found:
 
 ---
 
-Welcome to ODD Studio v3.3.4.
+Welcome to ODD Studio v3.3.6.
 
 You are about to plan and build something real — using a methodology called Outcome-Driven Development. Before we write a single line of code, we are going to get precise about three things:
 
@@ -59,7 +59,7 @@ Display this when existing state is found. Replace the bracketed values with act
 
 ---
 
-Welcome back to ODD Studio v3.3.4.
+Welcome back to ODD Studio v3.3.6.
 
 **Project:** [project.name]
 **Current Phase:** [state.currentPhase]

package/templates/AGENTS.md

@@ -5,13 +5,13 @@
 
 This project uses ODD Studio for planning and building. To activate the ODD coach:
 
-**In Codex:** Say `use ODD` or `start ODD` — there is no `/odd` slash command in Codex.
-The agent will read the coaching protocol below and guide you through planning or building.
+**In Codex:** Type `/odd` to start, or `/odd-status` to check the current state before resuming.
+If slash commands are unavailable in this workspace, `use ODD`, `start ODD`, or `begin ODD` are acceptable fallbacks.
 
 **In OpenCode:** Type `/odd` to start.
 
 When activated, read the full coaching protocol:
-- `plugins/odd-studio/skills/odd/SKILL.md` (Codex) or `.opencode/commands/odd/SKILL.md` (OpenCode)
+- `plugins/odd-studio/skills/odd/SKILL.md` (Codex) or `.opencode/odd/SKILL.md` (OpenCode)
 
 Then execute the startup state check documented in that file.
 
@@ -148,8 +148,10 @@ _Until then, the ODD defaults apply:_
 _This section is populated by Rachel during Step 9b of the planning phase._
 
 ## Session Start Protocol
-Every new session begins with the user saying **"use ODD"** or **"start ODD"**.
-When you see this, read the full coaching protocol from the skill file (see "How to Start ODD" above),
+Every new session begins with an explicit ODD command.
+In Codex and OpenCode, the primary entrypoint is `/odd`. In Codex, `/odd-status` is the status-only entrypoint.
+If Codex slash commands are unavailable, treat `use ODD`, `start ODD`, or `begin ODD` as `/odd`, `ODD status` as `/odd-status`, and `ODD build` as `/odd-build`.
+When you see one of these triggers, read the full coaching protocol from the skill file (see "How to Start ODD" above),
 then execute the startup state check from that skill exactly as written.
 
 Do not skip straight to persona naming or build questions.