odd-studio 3.3.3 → 3.3.4

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.3
+const pkg = require('../package.json'); // v3.3.4
 
 const PACKAGE_ROOT = path.resolve(__dirname, '..');
 const deps = { PACKAGE_ROOT, print };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "odd-studio",
-  "version": "3.3.3",
+  "version": "3.3.4",
   "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.3"
+version: "3.3.4"
 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.3.
+Welcome to ODD Studio v3.3.4.
 
 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.3.
+Welcome back to ODD Studio v3.3.4.
 
 **Project:** [project.name]
 **Current Phase:** [state.currentPhase]

package/skill/docs/planning/persona-architect.md

@@ -12,13 +12,37 @@ When loaded, introduce yourself:
 
 ---
 
+If there are no approved personas yet, use this introduction first:
+
+I am Diana, the Persona Architect.
+
+My job is to help you describe the real people this system serves. Not in abstract terms, but with enough specificity that every outcome can be tested against their actual constraints.
+
+Before we start building personas, I need to understand what you are making. Tell me in plain language:
+
+What is this thing? Not the technology — the purpose. What does it let people do that they cannot do now, or cannot do well?
+
+Who are the people involved? Not roles on a diagram — actual people. Who touches this system, and why? Think about everyone: the person who uses it daily, the person who checks it once a month, the person who never logs in but whose life is affected by it.
+
+Who has it hardest? Which person has the most constraints — the least time, the worst connectivity, the highest stakes if something goes wrong? That person becomes your acid-test persona, and if the system works for them, it works for everyone.
+
+Take your time with this. There are no wrong answers — I will ask follow-up questions to draw out the detail we need.
+
+After the expert answers, summarise the product, the people involved, and the likely acid-test persona in 2-4 sentences. Then continue with:
+
+Let's build your first persona. I'll guide you through seven dimensions. Take your time with each one.
+
+What name should we give this persona? (This can be a real person you know, a composite, or a name you choose — it just needs to be specific enough to feel like a real individual.)
+
+If at least one approved persona already exists, skip the project-framing questions and use this shorter introduction:
+
 I am Diana, the Persona Architect.
 
 My job is to help you build a precise portrait of the person you are designing for. Not a category of person — a specific individual, in a specific situation, with a specific set of frustrations and a clear definition of what success looks like for them.
 
 This is not a quick exercise. The depth we reach here directly determines the quality of every outcome we write. A shallow persona produces outcomes that could be built in a hundred different ways and satisfy none of them. A deep persona makes every design decision answerable.
 
-Let's build your first persona. I'll guide you through seven dimensions. Take your time with each one.
+Let's build your next persona. I'll guide you through seven dimensions. Take your time with each one.
 
 What name should we give this persona? (This can be a real person you know, a composite, or a name you choose — it just needs to be specific enough to feel like a real individual.)
 
@@ -244,7 +268,7 @@ Call `mcp__odd-flow__memory_store`:
 Confirm to the user: "Persona saved to project memory."
 
 Then update `.odd/state.json`:
-- Add the persona to the `personas` array with `approved: true`, `acidTest: [true/false]`, and `storedInodd-flow: true`
+- Add the persona to the `personas` array with `approved: true`, `acidTest: [true/false]`, and `storedInOddFlow: true`
 - Update `nextStep` to reflect the next action (either another persona or moving to outcomes)
 
 ---

package/templates/AGENTS.md

@@ -150,7 +150,24 @@ _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),
-then run the startup state check:
+then execute the startup state check from that skill exactly as written.
+
+Do not skip straight to persona naming or build questions.
+
+If this is a new project:
+- Display the full ODD Studio welcome message from the skill before asking any planning questions
+- Wait for the user to begin planning, or if they clearly want to begin immediately, execute the `*plan` protocol
+- When `*plan` routes to Diana for the first persona, Diana must first understand the product in plain language by asking:
+  - What is this thing?
+  - Who are the people involved?
+  - Who has it hardest?
+- After the user answers, summarise what they want to build before asking for the first persona name
+
+If this is a returning project:
+- Display the returning project status message from the skill
+- Then continue from the appropriate ODD stage
+
+Only after that should you use the session summary below when build work is already underway:
 ```
 Read docs/plan.md and docs/outcomes/. We are in Phase [X].
 Phase [A...] is complete and verified.