@open-product-primer/cli 0.9.0 → 0.11.0

package/dist/commands/init.js

@@ -128,5 +128,11 @@ function initCommand() {
             console.log('\n' + chalk_1.default.green('✓') + ` Agent skills installed: ${selectedAgents.join(', ')}`);
         }
         console.log('\nRun ' + chalk_1.default.cyan('oprim doctor') + ' to verify your setup.');
+        console.log('\n' +
+            chalk_1.default.bold('Next:') +
+            ' capture your first product decision. A bet is a time-bound commitment — what you\'re building, why now, and what would make you stop.' +
+            '\nOpen your AI agent and run ' +
+            chalk_1.default.cyan('/oprim:bet') +
+            ' to create one.');
     });
 }

package/dist/lib/install-agent.js

@@ -328,6 +328,8 @@ description: Create a new Product Decision Record in oprim/decisions/ with auto-
 
 Create a new Product Decision Record (PDR) in \`oprim/decisions/\`.
 
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
+
 ## Steps
 
 ### 1. Get the decision title
@@ -388,6 +390,12 @@ description: Create a new bet directory and bet-decision artifact in oprim/bets/
 
 Create a new bet in \`oprim/bets/\` and register it on the sequencing board.
 
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
+
+## What you're creating
+
+A bet is a product decision you're committing to explore: a problem worth solving, a hypothesis worth testing, or a direction worth taking. You'll name it, explain why now, and set a kill criterion so you know when to stop.
+
 ## Steps
 
 ### 1. Get the bet title
@@ -407,7 +415,10 @@ After receiving the title, validate: if fewer than 4 words OR fewer than 25 char
   - If "y": proceed with the original title
 
 ### 2. Assign the next BET ID
-Scan \`oprim/bets/\` for directories matching \`BET-(\\d+)\`. Extract all integers. Assign max+1, zero-padded to 3 digits. Default \`001\` if none.
+Scan both \`oprim/bets/\` and \`oprim/bets/archived/\` for directories whose names match \`BET-(\\d+)(-[^/]*)?\` (handles both \`BET-NNN/\` and \`BET-NNN-<slug>/\`). Extract the numeric part from each match. Assign max+1, zero-padded to 3 digits. Default \`001\` if none found in either location.
+
+### 2b. Derive the slug
+From the bet title: lowercase all characters, replace any character that is not a letter or digit with a hyphen, collapse consecutive hyphens to one, strip leading/trailing hyphens, truncate to 40 characters at the last hyphen boundary. This becomes \`<slug>\`. Example: "Add title slugs to bet directories for scannability" → \`add-title-slugs-to-bet-dirs-for\`.
 
 ### 3. Check sequence.yaml exists
 If \`oprim/sequence.yaml\` not found: report and stop — advise \`oprim init\`.
@@ -415,7 +426,7 @@ If \`oprim/sequence.yaml\` not found: report and stop — advise \`oprim init\`.
 ### 4. Gather content
 Ask: Decision (Build now / Defer / Kill, default Build now), Owner, Review date (YYYY-MM-DD), Why now, Alternatives considered, Expected outcomes (metric: baseline → target in timeframe), Kill criteria / rollback trigger, PDR links (optional).
 
-### 5. Write oprim/bets/BET-NNN/bet-decision.md
+### 5. Write oprim/bets/BET-NNN-<slug>/bet-decision.md
 \`\`\`
 # Decision: BET-NNN <title>
 <!-- Naming tip: verb + object [for context] — e.g. "Improve bet naming for scannability" not "Naming" -->
@@ -455,7 +466,7 @@ Read → parse YAML → append → write back (2-space indentation):
 
 ### 7. Prompt for optional discovery scaffolding
 Ask: "Do you want to scaffold a discovery.md now? (y/N)"
-- If "y": write \`oprim/bets/BET-NNN/discovery.md\` from the discovery template (same structure as \`oprim/templates/discovery.md\`).
+- If "y": write \`oprim/bets/BET-NNN-<slug>/discovery.md\` from the discovery template (same structure as \`oprim/templates/discovery.md\`).
 - If "n" or Enter: skip silently.
 
 ### 8. Report what was created
@@ -469,6 +480,8 @@ description: Create or append to a criteria.yaml contract for a bet, with struct
 
 Create or append to \`oprim/bets/BET-NNN/criteria.yaml\`.
 
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
+
 ## Steps
 
 ### 1. Identify the bet
@@ -517,11 +530,13 @@ If not: create with \`metrics:\` list.
 function archiveSkill() {
     return `---
 name: oprim-archive
-description: Archive a completed bet — moves it to oprim/bets/archived/BET-NNN/ and removes its sequence.yaml entry
+description: Archive a completed bet — moves it to oprim/bets/archived/ and removes its sequence.yaml entry
 ---
 
 Archive a completed bet by moving it to \`oprim/bets/archived/\` and removing it from \`sequence.yaml\`.
 
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
+
 ## Steps
 
 ### 1. Get the bet ID
@@ -532,11 +547,19 @@ If not provided, ask: "Which bet ID would you like to archive? (e.g., BET-005)"
 
 Normalize the input: accept \`bet-005\`, \`005\`, \`5\`, or \`BET-005\` — always treat as \`BET-NNN\` zero-padded to 3 digits.
 
-### 2. Check the bet directory exists
+### 2. Resolve the bet directory
+
+Look for the bet directory in \`oprim/bets/\` using two patterns:
+1. Exact match: \`oprim/bets/BET-NNN/\` (legacy non-slug format)
+2. Slug variant: any directory starting with \`BET-NNN-\` (e.g., \`BET-NNN-<slug>/\`)
+
+Use whichever pattern matches. Call this the **resolved directory name**.
 
-Check whether \`oprim/bets/BET-NNN/\` exists.
+If multiple directories match (e.g., both \`BET-NNN/\` and \`BET-NNN-slug/\` exist):
+- Report: "Ambiguous: found multiple directories for BET-NNN: [list them]. Please archive manually."
+- Stop.
 
-If not found:
+If neither pattern matches:
 - Report: "Bet BET-NNN was not found in oprim/bets/. Nothing was changed."
 - Stop.
 
@@ -566,9 +589,9 @@ Create the archive subfolder if it doesn't exist:
 mkdir -p oprim/bets/archived
 \`\`\`
 
-Move the directory:
+Move the resolved directory:
 \`\`\`bash
-mv oprim/bets/BET-NNN oprim/bets/archived/BET-NNN
+mv oprim/bets/<resolved-dir> oprim/bets/archived/<resolved-dir>
 \`\`\`
 
 ### 5. Remove the bet entry from sequence.yaml
@@ -581,7 +604,7 @@ Read \`oprim/sequence.yaml\`, parse it, and remove the entry with \`id: BET-NNN\
 ## Bet Archived
 
 **Bet:** BET-NNN
-**Archived to:** oprim/bets/archived/BET-NNN/
+**Archived to:** oprim/bets/archived/<resolved-dir>/
 **Removed from sequence.yaml:** ✓
 
 The bet is preserved in full at the archive location.
@@ -626,6 +649,8 @@ description: Validate and update the primer sequencing board — triage mode com
 
 Manage the primer sequencing board in \`oprim/sequence.yaml\`.
 
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
+
 ## Entry modes
 
 **Triage mode** — no intention provided: reads board state, computes health, surfaces specific actionable suggestions.
@@ -718,6 +743,8 @@ description: Create a KPI review artifact for a completed bet, pre-filled from c
 
 Create a KPI review in \`oprim/reviews/\`.
 
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
+
 ## Steps
 
 ### 1. Identify the bet
@@ -777,7 +804,7 @@ function pdrInlineContent() {
     return `Create a new PDR in \`oprim/decisions/\`. Scan for \`PDR-(\\d+)-\` to assign next ID (zero-padded, default 001). Gather: title, context, decision, alternatives, consequences, evidence, related bets/specs. Ask if superseding an existing PDR. Write \`oprim/decisions/PDR-NNN-<slug>.md\`. If superseding: update old PDR Status to "Superseded by PDR-NNN". Report what was created.`;
 }
 function betInlineContent() {
-    return `Create a new bet in \`oprim/bets/\`. Before asking for the title, show: "Naming tip: verb + object [for context] — Good: 'Improve bet naming for scannability' / Bad: 'Naming'". Scan \`BET-(\\d+)\` dirs for next ID (zero-padded, default 001). Check \`oprim/sequence.yaml\` exists (stop if not — advise oprim init). After receiving the title, validate: if fewer than 4 words OR fewer than 25 characters, warn "this title may be too vague", suggest a reformulation, and ask "Proceed anyway? (y/N)" — if "n", prompt for a revised title. Gather: decision (default Build now), owner, review date, why-now, alternatives, expected outcomes, kill criteria, PDR links. Write \`oprim/bets/BET-NNN/bet-decision.md\` with an inline naming tip comment in the header. Append entry to sequence.yaml backlog: \`{id, title, blocked_by: [], unlocks: [], requires_pdrs: []}\`. Then ask: "Do you want to scaffold a discovery.md now? (y/N)" — if "y", write \`oprim/bets/BET-NNN/discovery.md\` from the discovery template (sections: Problem Framing, User Research Signals, Competitive Context, Open Questions); if "n" or Enter, skip silently. Report what was created.`;
+    return `Create a new bet in \`oprim/bets/\`. First explain: "A bet is a product decision you're committing to explore — a problem worth solving, a hypothesis worth testing, or a direction worth taking. You'll name it, explain why now, and set a kill criterion." Then show: "Naming tip: verb + object [for context] — Good: 'Improve bet naming for scannability' / Bad: 'Naming'". Scan \`BET-(\\d+)\` dirs for next ID (zero-padded, default 001). Check \`oprim/sequence.yaml\` exists (stop if not — advise oprim init). After receiving the title, validate: if fewer than 4 words OR fewer than 25 characters, warn "this title may be too vague", suggest a reformulation, and ask "Proceed anyway? (y/N)" — if "n", prompt for a revised title. Gather: decision (default Build now), owner, review date, why-now, alternatives, expected outcomes, kill criteria, PDR links. Write \`oprim/bets/BET-NNN/bet-decision.md\` with an inline naming tip comment in the header. Append entry to sequence.yaml backlog: \`{id, title, blocked_by: [], unlocks: [], requires_pdrs: []}\`. Then ask: "Do you want to scaffold a discovery.md now? (y/N)" — if "y", write \`oprim/bets/BET-NNN/discovery.md\` from the discovery template (sections: Problem Framing, User Research Signals, Competitive Context, Open Questions); if "n" or Enter, skip silently. Report what was created.`;
 }
 function criteriaInlineContent() {
     return `Add metrics to \`oprim/bets/BET-NNN/criteria.yaml\`. Verify bet dir exists. Gather: metric ID, name, baseline, target, timeframe, launch date, segment. Ask source type (amplitude or bigquery). Amplitude: event, aggregation, denominator_event. BigQuery: table, metric_column, filter, aggregation, denominator_query. If file exists: append to metrics list (never overwrite). If not: create. Ask if adding more metrics. Report what was created.`;
@@ -826,7 +853,6 @@ nudge_flag=".claude/hooks/.sequence-nudge"
 # --- Archive co-archival block ---
 if [ -f "$archive_flag" ]; then
   change=$(tr -d '[:space:]' < "$archive_flag")
-  rm -f "$archive_flag"
 
   if [ -z "$change" ]; then
     latest=$(ls openspec/changes/archive/ 2>/dev/null | sort -r | head -1)
@@ -836,6 +862,7 @@ if [ -f "$archive_flag" ]; then
   if [ -n "$change" ]; then
     archive_dir=$(ls openspec/changes/archive/ 2>/dev/null | grep -F "$change" | sort -r | head -1)
     if [ -n "$archive_dir" ]; then
+      rm -f "$archive_flag"
       proposal="openspec/changes/archive/$archive_dir/proposal.md"
       if [ -f "$proposal" ]; then
         bet_id=$(grep -oE 'BET-[0-9]+' "$proposal" | head -1)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@open-product-primer/cli",
-  "version": "0.9.0",
+  "version": "0.11.0",
   "description": "Open Product Primer CLI — product decisions, sequencing, and KPI tracking for repositories",
   "keywords": [
     "product",