@open-product-primer/cli 2.2.0 → 2.4.0

package/dist/commands/doctor.js

@@ -231,7 +231,7 @@ function doctorCommand() {
             required: false,
         });
         // ── Discovery checks — warn if bet is missing discovery.md ───────────────
-        const betsDir = path.join(primerDir, 'bets');
+        const betsDir = path.join(primerDir, 'bets', 'pending');
         if (fs.existsSync(betsDir)) {
             const betEntries = fs.readdirSync(betsDir, { withFileTypes: true });
             for (const entry of betEntries) {

package/dist/commands/init.js

@@ -64,7 +64,7 @@ function initCommand() {
         const specFramework = await (0, install_agent_1.promptFrameworkSelection)(projectRoot);
         const primerDir = path.join(projectRoot, 'oprim');
         (0, scaffold_1.ensureDir)(path.join(primerDir, 'decisions'));
-        (0, scaffold_1.ensureDir)(path.join(primerDir, 'bets'));
+        (0, scaffold_1.ensureDir)(path.join(primerDir, 'bets', 'pending'));
         (0, scaffold_1.ensureDir)(path.join(primerDir, 'reviews'));
         (0, scaffold_1.ensureDir)(path.join(primerDir, 'notes'));
         (0, scaffold_1.ensureDir)(path.join(primerDir, 'templates'));
@@ -94,7 +94,7 @@ function initCommand() {
             (0, scaffold_1.writeFile)(path.join(primerDir, 'index.md'), (0, templates_1.indexTemplate)(projectName));
         }
         (0, scaffold_1.writeFileIfAbsent)(path.join(primerDir, 'decisions', '.gitkeep'), '');
-        (0, scaffold_1.writeFileIfAbsent)(path.join(primerDir, 'bets', '.gitkeep'), '');
+        (0, scaffold_1.writeFileIfAbsent)(path.join(primerDir, 'bets', 'pending', '.gitkeep'), '');
         (0, scaffold_1.writeFileIfAbsent)(path.join(primerDir, 'reviews', '.gitkeep'), '');
         (0, scaffold_1.writeFileIfAbsent)(path.join(primerDir, 'notes', '.gitkeep'), '');
         console.log('\n' + chalk_1.default.green('✓') + ' oprim/ workspace created');

package/dist/commands/ovw.js

@@ -228,7 +228,7 @@ function ovwCommand() {
         .action(() => {
         const projectRoot = process.cwd();
         const sequencePath = path.join(projectRoot, 'oprim', 'sequence.yaml');
-        const betsDir = path.join(projectRoot, 'oprim', 'bets');
+        const betsDir = path.join(projectRoot, 'oprim', 'bets', 'pending');
         if (!fs.existsSync(sequencePath)) {
             console.error("No oprim/sequence.yaml found — run 'oprim init' first");
             process.exit(1);

package/dist/commands/validate.js

@@ -65,10 +65,10 @@ function printReport(checks) {
     console.log(`\n${passed}/${checks.length} checks passed.`);
 }
 function runDiff(projectRoot, betIdInput) {
-    const betsDir = path.join(projectRoot, 'oprim', 'bets');
+    const betsDir = path.join(projectRoot, 'oprim', 'bets', 'pending');
     const resolvedDir = (0, spec_delta_1.resolveBetDirectory)(betsDir, betIdInput);
     if (!resolvedDir) {
-        console.error(chalk_1.default.red(`Bet ${betIdInput} was not found in oprim/bets/.`));
+        console.error(chalk_1.default.red(`Bet ${betIdInput} was not found in oprim/bets/pending/.`));
         process.exitCode = 1;
         return;
     }

package/dist/lib/measure.js

@@ -230,12 +230,10 @@ async function runBigQueryMetric(sqlPath) {
 }
 // ─── Criteria scanner (used by doctor) ───────────────────────────────────────
 function scanCriteriaForSourceType(projectRoot, sourceType) {
-    const betsDir = path.join(projectRoot, 'oprim', 'bets');
+    const betsDir = path.join(projectRoot, 'oprim', 'bets', 'pending');
     if (!fs.existsSync(betsDir))
         return false;
     for (const entry of fs.readdirSync(betsDir)) {
-        if (entry === 'archived')
-            continue;
         const criteriaPath = path.join(betsDir, entry, 'criteria.yaml');
         if (!fs.existsSync(criteriaPath))
             continue;

package/dist/lib/validate-checks.js

@@ -73,7 +73,7 @@ function isPromoted(betDecisionContent) {
  * change) that has no criteria.yaml alongside it. Un-promoted bets are not checked.
  */
 function checkBetDefinitionOfDone(projectRoot, checks) {
-    const betsDir = path.join(projectRoot, 'oprim', 'bets');
+    const betsDir = path.join(projectRoot, 'oprim', 'bets', 'pending');
     for (const entry of activeBetDirs(betsDir)) {
         const betDir = path.join(betsDir, entry.name);
         const decisionPath = path.join(betDir, 'bet-decision.md');
@@ -88,7 +88,7 @@ function checkBetDefinitionOfDone(projectRoot, checks) {
             checks.push({
                 name: `bet: ${betId} promoted without criteria.yaml`,
                 pass: false,
-                note: `Add criteria.yaml to oprim/bets/${entry.name}/, or run the oprim-criteria skill`,
+                note: `Add criteria.yaml to oprim/bets/pending/${entry.name}/, or run the oprim-criteria skill`,
                 required: false,
             });
         }
@@ -99,7 +99,7 @@ function checkBetDefinitionOfDone(projectRoot, checks) {
  * longer text-matches (whitespace-insensitive) current truth.
  */
 function checkSpecDeltaDrift(projectRoot, checks) {
-    const betsDir = path.join(projectRoot, 'oprim', 'bets');
+    const betsDir = path.join(projectRoot, 'oprim', 'bets', 'pending');
     for (const entry of activeBetDirs(betsDir)) {
         const betId = extractBetId(entry.name);
         const specsDir = path.join(betsDir, entry.name, 'specs');
@@ -133,7 +133,7 @@ function checkSpecDeltaDrift(projectRoot, checks) {
 }
 /** Surfaces overlapping requirement headers across active bets' spec deltas. */
 function checkCrossBetConflicts(projectRoot, checks) {
-    const betsDir = path.join(projectRoot, 'oprim', 'bets');
+    const betsDir = path.join(projectRoot, 'oprim', 'bets', 'pending');
     for (const conflict of (0, spec_delta_1.findCrossBetConflicts)(betsDir)) {
         checks.push({
             name: `spec-delta: ${extractBetId(conflict.betA)} and ${extractBetId(conflict.betB)} both touch "${conflict.header}" in ${conflict.capability}`,

package/dist/workflows/archive.inline.md

@@ -2,9 +2,9 @@
 Archive a completed bet.
 
 1. Ask for bet ID (accept bet-005, 005, 5, BET-005 — normalize to BET-NNN).
-2. Verify `oprim/bets/BET-NNN/` exists.
-3. Check `oprim/sequence.yaml` for entries where `blocked_by` or `unlocks` reference the target bet — warn if found. Also check other active bet dirs for delta specs against the same requirement (matching `### Requirement:` headers, whitespace-insensitive) — warn if an overlap is found. Ask "Archive anyway? (y/N)" if either warning fires.
-4. If `oprim/bets/BET-NNN/specs/` exists, fold each capability's `## ADDED`/`## MODIFIED`/`## REMOVED Requirements` delta into `oprim/specs/<capability>/spec.md` (matching by `### Requirement:` header; create the current-truth file if the delta is entirely ADDED) — last-write-wins on overlaps, no 3-way merge. Skip this step entirely if no `specs/` dir is present.
-5. Move directory: `oprim/bets/BET-NNN → oprim/bets/archived/BET-NNN`.
+2. Verify `oprim/bets/pending/BET-NNN/` exists.
+3. Check `oprim/sequence.yaml` for entries where `blocked_by` or `unlocks` reference the target bet — warn if found. Also check other active bet dirs for delta specs against the same requirement (matching `### Requirement:` headers, whitespace-insensitive) — warn if an overlap is found. Also check the bet's `tasks.md` (if present) for unchecked `- [ ]` items — warn with the count if any remain. Ask "Archive anyway? (y/N)" if any warning fires.
+4. If `oprim/bets/pending/BET-NNN/specs/` exists, fold each capability's `## ADDED`/`## MODIFIED`/`## REMOVED Requirements` delta into `oprim/specs/<capability>/spec.md` (matching by `### Requirement:` header; create the current-truth file if the delta is entirely ADDED) — last-write-wins on overlaps, no 3-way merge. Skip this step entirely if no `specs/` dir is present.
+5. Move directory: `oprim/bets/pending/BET-NNN → oprim/bets/archived/BET-NNN`.
 6. Remove the bet entry from `oprim/sequence.yaml`.
 7. Report what was done.

package/dist/workflows/archive.template.md

@@ -19,8 +19,8 @@ Normalize the input: accept `bet-005`, `005`, `5`, or `BET-005` — always treat
 
 ### 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)
+Look for the bet directory in `oprim/bets/pending/` using two patterns:
+1. Exact match: `oprim/bets/pending/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**.
@@ -30,17 +30,19 @@ If multiple directories match (e.g., both `BET-NNN/` and `BET-NNN-slug/` exist):
 - Stop.
 
 If neither pattern matches:
-- Report: "Bet BET-NNN was not found in oprim/bets/. Nothing was changed."
+- Report: "Bet BET-NNN was not found in oprim/bets/pending/. Nothing was changed."
 - Stop.
 
-### 3. Check for active dependencies and concurrent spec-delta conflicts
+### 3. Check for active dependencies, concurrent spec-delta conflicts, and incomplete tasks.md
 
 Read `oprim/sequence.yaml`. Scan every entry across all buckets (now, next, later, backlog) for any entry whose `blocked_by` or `unlocks` list contains the target bet ID.
 
-Separately, if `oprim/bets/<resolved-dir>/specs/` exists: for each `<capability>/spec.md` delta file under it, extract every `### Requirement:` header from its `## ADDED`/`## MODIFIED`/`## REMOVED Requirements` sections. Then scan every other bet directory directly under `oprim/bets/` (excluding `archived/` and the bet being archived) for a `specs/<capability>/spec.md` file for the same capability; if one exists, extract its `### Requirement:` headers too. Flag any header that matches (whitespace-insensitive) between the archiving bet's delta and another still-active bet's delta as an **overlap**.
+Separately, if `oprim/bets/pending/<resolved-dir>/specs/` exists: for each `<capability>/spec.md` delta file under it, extract every `### Requirement:` header from its `## ADDED`/`## MODIFIED`/`## REMOVED Requirements` sections. Then scan every other bet directory directly under `oprim/bets/pending/` (excluding the bet being archived) for a `specs/<capability>/spec.md` file for the same capability; if one exists, extract its `### Requirement:` headers too. Flag any header that matches (whitespace-insensitive) between the archiving bet's delta and another still-active bet's delta as an **overlap**.
 
-If either sequence.yaml dependents or delta overlaps are found:
-- Show a combined warning listing each dependent entry and each overlapping requirement.
+Separately, if `oprim/bets/pending/<resolved-dir>/tasks.md` exists: count the number of unchecked `- [ ]` items in it. If one or more remain, flag this as an **incomplete-tasks warning**. If `tasks.md` doesn't exist, or every item is checked (`- [x]`), this contributes nothing to the warning.
+
+If any of sequence.yaml dependents, delta overlaps, or an incomplete tasks.md are found:
+- Show a combined warning listing each dependent entry, each overlapping requirement, and (if applicable) the incomplete-tasks count.
 
   Example:
   ```
@@ -48,18 +50,19 @@ If either sequence.yaml dependents or delta overlaps are found:
     - BET-007 (blocked_by: [BET-005])
     - BET-008 (unlocks: [BET-005])
   ⚠ Warning: BET-005's delta for requirement "The system SHALL ..." in capability foo overlaps with active bet BET-009's delta for the same requirement. Archiving BET-005 now applies its version to oprim/specs/foo/spec.md; if BET-009 archives later, its version will overwrite this requirement again (last-write-wins — no 3-way merge is attempted).
+  ⚠ Warning: BET-005's tasks.md has 3 unchecked item(s) — implementation may be incomplete.
   ```
 - Ask: "Archive BET-NNN anyway? (y/N)"
   - If "n" or Enter: stop, no changes made.
   - If "y": proceed.
 
-If neither is found: proceed without warning.
+If none are found: proceed without warning.
 
 ### 4. Fold spec deltas into current truth
 
-If `oprim/bets/<resolved-dir>/specs/` does not exist: skip this step entirely and go to Step 5 — archive behavior is unchanged from before spec deltas existed.
+If `oprim/bets/pending/<resolved-dir>/specs/` does not exist: skip this step entirely and go to Step 5 — archive behavior is unchanged from before spec deltas existed.
 
-Otherwise, for each capability subdirectory under `oprim/bets/<resolved-dir>/specs/` containing a `spec.md`:
+Otherwise, for each capability subdirectory under `oprim/bets/pending/<resolved-dir>/specs/` containing a `spec.md`:
 
 1. Read the delta file's `## ADDED Requirements` / `## MODIFIED Requirements` / `## REMOVED Requirements` sections. Each `### Requirement:` block runs from its header through its body and any `#### Scenario:` sub-entries, up to the next `### Requirement:` or `## ` header.
 2. Read `oprim/specs/<capability>/spec.md` if it exists (current truth uses a single flat `## Requirements` section).
@@ -85,7 +88,7 @@ mkdir -p oprim/bets/archived
 
 Move the resolved directory:
 ```bash
-mv oprim/bets/<resolved-dir> oprim/bets/archived/<resolved-dir>
+mv oprim/bets/pending/<resolved-dir> oprim/bets/archived/<resolved-dir>
 ```
 
 ### 6. Remove the bet entry from sequence.yaml

package/dist/workflows/bet.cursor-command.md

@@ -1 +1 @@
-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). Read `oprim/config.yaml`'s `rules.bet` — if non-empty, apply it as additional guidance and reflect it in the generated content; if empty, behavior is unchanged. 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.
+Create a new bet in `oprim/bets/pending/`. 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 `oprim/bets/pending/BET-(\d+)` and `oprim/bets/archived/BET-(\d+)` dirs for next ID (zero-padded, default 001). Check `oprim/sequence.yaml` exists (stop if not — advise oprim init). Read `oprim/config.yaml`'s `rules.bet` — if non-empty, apply it as additional guidance and reflect it in the generated content; if empty, behavior is unchanged. 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/pending/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/pending/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.

package/dist/workflows/bet.inline.md

@@ -1,13 +1,13 @@
 ### Bet authoring (oprim-bet)
-Create a new bet in `oprim/bets/` and register it on the sequencing board.
+Create a new bet in `oprim/bets/pending/` and register it on the sequencing board.
 
 1. Show naming tip: "verb + object [for context] — e.g. 'Improve bet naming for scannability'"
 2. Ask for the bet title. Validate: fewer than 4 words OR fewer than 25 chars → warn, suggest reformulation, ask "Proceed anyway? (y/N)".
-3. Assign next BET ID: scan `oprim/bets/BET-(\d+)` dirs, max+1 zero-padded to 3 digits (default 001).
+3. Assign next BET ID: scan `oprim/bets/pending/BET-(\d+)` and `oprim/bets/archived/BET-(\d+)` dirs, max+1 zero-padded to 3 digits (default 001).
 4. Check `oprim/sequence.yaml` exists — stop if not, advise `oprim init`.
 4b. Read `oprim/config.yaml`'s `rules.bet` — if non-empty, apply it as additional guidance and reflect it in the generated content; if empty, behavior is unchanged.
 5. Gather: decision (default Build now), owner, review date (YYYY-MM-DD), why now, alternatives, expected outcomes, kill criteria, PDR links.
-6. Write `oprim/bets/BET-NNN/bet-decision.md` with all fields.
+6. Write `oprim/bets/pending/BET-NNN/bet-decision.md` with all fields.
 7. Append to `oprim/sequence.yaml` backlog: `{id, title, blocked_by: [], unlocks: [], requires_pdrs: []}`.
-8. Ask: "Scaffold a discovery.md now? (y/N)" — if "y", write `oprim/bets/BET-NNN/discovery.md`.
+8. Ask: "Scaffold a discovery.md now? (y/N)" — if "y", write `oprim/bets/pending/BET-NNN/discovery.md`.
 9. Report what was created.

package/dist/workflows/bet.schema.yaml

@@ -1,7 +1,7 @@
 id: bet
 skillName: oprim-bet
 title: null
-description: Create a new bet directory and bet-decision artifact in oprim/bets/, and add the bet to oprim/sequence.yaml backlog
+description: Create a new bet directory and bet-decision artifact in oprim/bets/pending/, and add the bet to oprim/sequence.yaml backlog
 cursorDescription: Create a new bet decision and register it on the sequencing board
 claude:
   skill: true

package/dist/workflows/bet.template.md

@@ -1,9 +1,9 @@
 ---
 name: oprim-bet
-description: Create a new bet directory and bet-decision artifact in oprim/bets/, and add the bet to oprim/sequence.yaml backlog
+description: Create a new bet directory and bet-decision artifact in oprim/bets/pending/, and add the bet to oprim/sequence.yaml backlog
 ---
 
-Create a new bet in `oprim/bets/` and register it on the sequencing board.
+Create a new bet in `oprim/bets/pending/` 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.
 
@@ -30,7 +30,7 @@ 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 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.
+Scan both `oprim/bets/pending/` 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`.
@@ -57,7 +57,7 @@ Then ask about each of the four risk dimensions (Low / Medium / High + short rat
 Read `oprim/templates/bet-decision.md`. If it begins with a YAML frontmatter block (`---` ... `---`), this workspace has OKF frontmatter enabled. Ask for a one-line description and comma-separated tags (subject-area keywords). Prepare a frontmatter block with `type: bet-decision`, `title: <title>`, `description: <description>`, `tags: [<tags>]`, `timestamp: <today's date, ISO 8601>`, to prepend in step 5.
 If no frontmatter block is found in the template, skip this step — write the file with no frontmatter, matching current behavior.
 
-### 5. Write oprim/bets/BET-NNN-<slug>/bet-decision.md
+### 5. Write oprim/bets/pending/BET-NNN-<slug>/bet-decision.md
 Prepend the frontmatter block from step 4b, if one was prepared.
 ```
 # Decision: BET-NNN <title>
@@ -108,7 +108,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-<slug>/discovery.md` from the discovery template (same structure as `oprim/templates/discovery.md`).
+- If "y": write `oprim/bets/pending/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

package/dist/workflows/criteria.cursor-command.md

@@ -1 +1 @@
-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.
+Add metrics to `oprim/bets/pending/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.

package/dist/workflows/criteria.inline.md

@@ -1,5 +1,5 @@
 ### Criteria authoring (oprim-criteria)
-Create or append to `oprim/bets/BET-NNN/criteria.yaml`.
+Create or append to `oprim/bets/pending/BET-NNN/criteria.yaml`.
 
 1. Ask which bet (e.g. BET-042). Verify dir exists.
 2. Gather: metric ID (snake_case), name, baseline, target, timeframe, launch date, segment.

package/dist/workflows/criteria.template.md

@@ -3,7 +3,7 @@ name: oprim-criteria
 description: Create or append to a criteria.yaml contract for a bet, with structured Amplitude and BigQuery source mapping
 ---
 
-Create or append to `oprim/bets/BET-NNN/criteria.yaml`.
+Create or append to `oprim/bets/pending/BET-NNN/criteria.yaml`.
 
 **Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
 
@@ -13,7 +13,7 @@ Create or append to `oprim/bets/BET-NNN/criteria.yaml`.
 If not provided, ask: "Which bet are you adding criteria for? (e.g. BET-042)"
 
 ### 2. Verify bet exists
-If `oprim/bets/BET-NNN/` not found: report and stop — advise using the `oprim-bet` skill first.
+If `oprim/bets/pending/BET-NNN/` not found: report and stop — advise using the `oprim-bet` skill first.
 
 ### 3. Gather metric details
 Ask: metric ID (snake_case), metric name, baseline (numeric), target (numeric), timeframe, launch date (YYYY-MM-DD or TBD), segment (optional).

package/dist/workflows/note.template.md

@@ -61,6 +61,6 @@ timestamp: <today, ISO 8601>
 OKF tier: same as above, with `description: "<description>"` inserted immediately after `title`.
 
 ### 8. Link back from referenced bets
-For each BET-ID gathered in step 5: read `oprim/bets/BET-NNN/bet-decision.md`, and add `- Notes: NOTE-NNN` under its `## Links` section (append to an existing `Notes:` line, or add a new one).
+For each BET-ID gathered in step 5: read `oprim/bets/pending/BET-NNN/bet-decision.md`, and add `- Notes: NOTE-NNN` under its `## Links` section (append to an existing `Notes:` line, or add a new one).
 
 ### 9. Report what was created

package/dist/workflows/promote.native.template.md

@@ -10,20 +10,20 @@ Promote an atomic note into a bet, or a prioritized bet into a capability spec.
 
 ## A. Bet → native oprim spec
 
-1. **Locate the bet** — read `oprim/bets/BET-XXX/bet-decision.md`
+1. **Locate the bet** — read `oprim/bets/pending/BET-XXX/bet-decision.md`
 2. **Validate status** — decision must be "Build now"
 3. **Check authority boundary** — confirm primer artifact owns why/order/outcome only
-4. **Generate the native spec delta(s)** — for each capability listed under the bet's `## Capabilities` section (or a single capability derived from the bet title if none is listed), invoke the `oprim-spec` skill with this bet as context to write `oprim/bets/BET-XXX/specs/<capability>/spec.md` — a delta using `## ADDED`/`## MODIFIED`/`## REMOVED Requirements` headers reflecting the bet's why/outcome. No OpenSpec change directory is created and OpenSpec need not be installed. Nothing is written to `oprim/specs/<capability>/spec.md` (current truth) at promote time — that only happens when this bet is archived.
-5. **Link artifacts** — add `- Spec (delta): oprim/bets/BET-XXX/specs/<capability>/spec.md` (one line per capability) to the bet-decision `## Links` section
-6. **Copy criteria** — if `oprim/bets/BET-XXX/criteria.yaml` exists, note it alongside the spec link
+4. **Generate the native spec delta(s)** — for each capability listed under the bet's `## Capabilities` section (or a single capability derived from the bet title if none is listed), invoke the `oprim-spec` skill with this bet as context to write `oprim/bets/pending/BET-XXX/specs/<capability>/spec.md` — a delta using `## ADDED`/`## MODIFIED`/`## REMOVED Requirements` headers reflecting the bet's why/outcome. No OpenSpec change directory is created and OpenSpec need not be installed. Nothing is written to `oprim/specs/<capability>/spec.md` (current truth) at promote time — that only happens when this bet is archived.
+5. **Link artifacts** — add `- Spec (delta): oprim/bets/pending/BET-XXX/specs/<capability>/spec.md` (one line per capability) to the bet-decision `## Links` section
+6. **Copy criteria** — if `oprim/bets/pending/BET-XXX/criteria.yaml` exists, note it alongside the spec link
 7. **Report** — show what was created and linked, and note that merge-on-archive will fold the delta into `oprim/specs/` when the bet archives
 
 ## B. Note → Bet
 
 1. **Locate the note** — read `oprim/notes/NOTE-XXX-<slug>.md`
-2. **Assign the next BET ID** — scan both `oprim/bets/` and `oprim/bets/archived/` for directories matching `BET-(\d+)(-[^/]*)?`, max+1 zero-padded to 3 digits (default 001) — same convention `oprim-bet` uses
+2. **Assign the next BET ID** — scan both `oprim/bets/pending/` and `oprim/bets/archived/` for directories matching `BET-(\d+)(-[^/]*)?`, max+1 zero-padded to 3 digits (default 001) — same convention `oprim-bet` uses
 3. **Derive the slug** from the note's title (lowercase, non-alphanumeric → hyphen, collapse/trim hyphens, truncate to 40 chars at a hyphen boundary)
-4. **Draft the bet** — write `oprim/bets/BET-NNN-<slug>/bet-decision.md` from the standard bet-decision structure, pre-filling only `## Why now` from the note's body. Leave `Alternatives considered`, `Expected outcomes`, and `Kill criteria / rollback trigger` as template placeholders — draft from the note, don't fabricate content it doesn't support. Ask for `Owner` and `Review date`; default `Decision: Build now` and `Date` to today.
+4. **Draft the bet** — write `oprim/bets/pending/BET-NNN-<slug>/bet-decision.md` from the standard bet-decision structure, pre-filling only `## Why now` from the note's body. Leave `Alternatives considered`, `Expected outcomes`, and `Kill criteria / rollback trigger` as template placeholders — draft from the note, don't fabricate content it doesn't support. Ask for `Owner` and `Review date`; default `Decision: Build now` and `Date` to today.
 5. **Register the new bet** — append to `oprim/sequence.yaml` backlog: `{id, title, blocked_by: [], unlocks: [], requires_pdrs: []}`
 6. **Link back** — add `Bets: BET-NNN` to the note (creating or extending its `## Bets` section)
 7. **Report** — show the new bet's path and flag that `Alternatives considered`, `Expected outcomes`, and `Kill criteria` still need authoring before this bet can itself be promoted

package/dist/workflows/promote.none.template.md

@@ -10,16 +10,16 @@ Promote an atomic note into a bet, or a prioritized bet into a capability spec.
 
 ## A. Bet → spec (no framework configured)
 
-1. **Locate the bet** — read `oprim/bets/BET-XXX/bet-decision.md`
+1. **Locate the bet** — read `oprim/bets/pending/BET-XXX/bet-decision.md`
 2. **Validate status** — decision must be "Build now"
 3. **Report and stop** — no speccing framework is configured (`integrations.spec_framework: none`). Add `- Spec: none (no speccing framework configured)` to the bet-decision `## Links` section. No spec artifact is created.
 
 ## B. Note → Bet
 
 1. **Locate the note** — read `oprim/notes/NOTE-XXX-<slug>.md`
-2. **Assign the next BET ID** — scan both `oprim/bets/` and `oprim/bets/archived/` for directories matching `BET-(\d+)(-[^/]*)?`, max+1 zero-padded to 3 digits (default 001) — same convention `oprim-bet` uses
+2. **Assign the next BET ID** — scan both `oprim/bets/pending/` and `oprim/bets/archived/` for directories matching `BET-(\d+)(-[^/]*)?`, max+1 zero-padded to 3 digits (default 001) — same convention `oprim-bet` uses
 3. **Derive the slug** from the note's title (lowercase, non-alphanumeric → hyphen, collapse/trim hyphens, truncate to 40 chars at a hyphen boundary)
-4. **Draft the bet** — write `oprim/bets/BET-NNN-<slug>/bet-decision.md` from the standard bet-decision structure, pre-filling only `## Why now` from the note's body. Leave `Alternatives considered`, `Expected outcomes`, and `Kill criteria / rollback trigger` as template placeholders — draft from the note, don't fabricate content it doesn't support. Ask for `Owner` and `Review date`; default `Decision: Build now` and `Date` to today.
+4. **Draft the bet** — write `oprim/bets/pending/BET-NNN-<slug>/bet-decision.md` from the standard bet-decision structure, pre-filling only `## Why now` from the note's body. Leave `Alternatives considered`, `Expected outcomes`, and `Kill criteria / rollback trigger` as template placeholders — draft from the note, don't fabricate content it doesn't support. Ask for `Owner` and `Review date`; default `Decision: Build now` and `Date` to today.
 5. **Register the new bet** — append to `oprim/sequence.yaml` backlog: `{id, title, blocked_by: [], unlocks: [], requires_pdrs: []}`
 6. **Link back** — add `Bets: BET-NNN` to the note (creating or extending its `## Bets` section)
 7. **Report** — show the new bet's path and flag that `Alternatives considered`, `Expected outcomes`, and `Kill criteria` still need authoring before this bet can itself be promoted

package/dist/workflows/promote.openspec.template.md

@@ -10,7 +10,7 @@ Promote an atomic note into a bet, or a prioritized bet into a capability spec.
 
 ## A. Bet → OpenSpec change
 
-1. **Locate the bet** — read `oprim/bets/BET-XXX/bet-decision.md`
+1. **Locate the bet** — read `oprim/bets/pending/BET-XXX/bet-decision.md`
 2. **Validate status** — decision must be "Build now"
 3. **Check authority boundary** — confirm primer artifact owns why/order/outcome only
 4. **Create OpenSpec change** — derive the change name as `bet-NNN-<slug>` where `NNN` is the zero-padded bet number (e.g. BET-004 → `bet-004`) and `<slug>` is a short kebab-case summary of the change. Then invoke the `/openspec-propose` skill (or `/opsx:propose`) with that name to create the change directory with **all required artifacts**: `proposal.md`, `design.md`, `tasks.md`, and `specs/<capability>/spec.md` for every capability listed under `## Capabilities`.
@@ -20,7 +20,7 @@ Promote an atomic note into a bet, or a prioritized bet into a capability spec.
 5. **Link artifacts**:
    - Add OpenSpec change path to bet-decision `## Links` section
    - Add bet ID to OpenSpec proposal `## Context` section
-6. **Copy criteria** — if `oprim/bets/BET-XXX/criteria.yaml` exists, link it from OpenSpec proposal
+6. **Copy criteria** — if `oprim/bets/pending/BET-XXX/criteria.yaml` exists, link it from OpenSpec proposal
 7. **Verify completeness** — confirm the change directory contains:
    - `proposal.md`
    - `design.md`
@@ -32,9 +32,9 @@ Promote an atomic note into a bet, or a prioritized bet into a capability spec.
 ## B. Note → Bet
 
 1. **Locate the note** — read `oprim/notes/NOTE-XXX-<slug>.md`
-2. **Assign the next BET ID** — scan both `oprim/bets/` and `oprim/bets/archived/` for directories matching `BET-(\d+)(-[^/]*)?`, max+1 zero-padded to 3 digits (default 001) — same convention `oprim-bet` uses
+2. **Assign the next BET ID** — scan both `oprim/bets/pending/` and `oprim/bets/archived/` for directories matching `BET-(\d+)(-[^/]*)?`, max+1 zero-padded to 3 digits (default 001) — same convention `oprim-bet` uses
 3. **Derive the slug** from the note's title (lowercase, non-alphanumeric → hyphen, collapse/trim hyphens, truncate to 40 chars at a hyphen boundary)
-4. **Draft the bet** — write `oprim/bets/BET-NNN-<slug>/bet-decision.md` from the standard bet-decision structure, pre-filling only `## Why now` from the note's body. Leave `Alternatives considered`, `Expected outcomes`, and `Kill criteria / rollback trigger` as template placeholders — draft from the note, don't fabricate content it doesn't support. Ask for `Owner` and `Review date`; default `Decision: Build now` and `Date` to today.
+4. **Draft the bet** — write `oprim/bets/pending/BET-NNN-<slug>/bet-decision.md` from the standard bet-decision structure, pre-filling only `## Why now` from the note's body. Leave `Alternatives considered`, `Expected outcomes`, and `Kill criteria / rollback trigger` as template placeholders — draft from the note, don't fabricate content it doesn't support. Ask for `Owner` and `Review date`; default `Decision: Build now` and `Date` to today.
 5. **Register the new bet** — append to `oprim/sequence.yaml` backlog: `{id, title, blocked_by: [], unlocks: [], requires_pdrs: []}`
 6. **Link back** — add `Bets: BET-NNN` to the note (creating or extending its `## Bets` section)
 7. **Report** — show the new bet's path and flag that `Alternatives considered`, `Expected outcomes`, and `Kill criteria` still need authoring before this bet can itself be promoted

package/dist/workflows/review.cursor-command.md

@@ -1 +1 @@
-Create KPI review in `oprim/reviews/YYYY-MM-DD-BET-NNN-kpi.md`. Read `oprim/config.yaml`'s `rules.review` — if non-empty, apply it as additional guidance and reflect it in the generated content; if empty, behavior is unchanged. Read `criteria.yaml` for pre-fill (baseline/target). Check `oprim/bets/BET-NNN/measurements/` for `run-*.yaml` files — if found, use the most recent to pre-populate actuals and status (include "Actuals from run: YYYY-MM-DD" note). If no run result, ask for each metric's actual value. Status: actual >= target → hit, actual < target → missed, not provided → pending. Ask reviewer name and decision quality notes. Write review with metric table and Actions checklist. Report what was created.
+Create KPI review in `oprim/reviews/YYYY-MM-DD-BET-NNN-kpi.md`. Read `oprim/config.yaml`'s `rules.review` — if non-empty, apply it as additional guidance and reflect it in the generated content; if empty, behavior is unchanged. Read `criteria.yaml` for pre-fill (baseline/target). Check `oprim/bets/pending/BET-NNN/measurements/` for `run-*.yaml` files — if found, use the most recent to pre-populate actuals and status (include "Actuals from run: YYYY-MM-DD" note). If no run result, ask for each metric's actual value. Status: actual >= target → hit, actual < target → missed, not provided → pending. Ask reviewer name and decision quality notes. Write review with metric table and Actions checklist. Report what was created.

package/dist/workflows/review.inline.md

@@ -3,7 +3,7 @@ Create a KPI review artifact in `oprim/reviews/`.
 
 1. Ask which bet (e.g. BET-042).
 1b. Read `oprim/config.yaml`'s `rules.review` — if non-empty, apply it as additional guidance and reflect it in the generated content; if empty, behavior is unchanged.
-2. Read `oprim/bets/BET-NNN/criteria.yaml` for pre-fill. Check `oprim/bets/BET-NNN/measurements/` for `run-*.yaml` — use most recent if present.
+2. Read `oprim/bets/pending/BET-NNN/criteria.yaml` for pre-fill. Check `oprim/bets/pending/BET-NNN/measurements/` for `run-*.yaml` — use most recent if present.
 3. If no run result, ask for each metric's actual value.
 4. Status: actual >= target → hit; actual < target → missed; not provided → pending.
 5. Ask reviewer name and decision quality notes.

package/dist/workflows/review.template.md

@@ -17,10 +17,10 @@ Read `oprim/config.yaml`. If it has a non-empty `rules.review` value, treat it a
 
 ### 2. Load criteria and check for a run result
 
-Read `oprim/bets/BET-NNN/criteria.yaml` if it exists (pre-fills baseline and target).
+Read `oprim/bets/pending/BET-NNN/criteria.yaml` if it exists (pre-fills baseline and target).
 If not found: inform user and continue with empty metrics list.
 
-**Check for measurement run result:** Scan `oprim/bets/BET-NNN/measurements/` for files matching `run-*.yaml`. If any exist, sort by filename (date-based) and read the most recent.
+**Check for measurement run result:** Scan `oprim/bets/pending/BET-NNN/measurements/` for files matching `run-*.yaml`. If any exist, sort by filename (date-based) and read the most recent.
 
 **If a run result exists:** use it to pre-populate actuals and status for every metric. Skip step 3 for those metrics. Note the run date — include "Actuals from run: YYYY-MM-DD" in the review artifact.
 

package/dist/workflows/spec-authoring.schema.yaml

@@ -1,7 +1,7 @@
 id: spec-authoring
 skillName: oprim-spec
 title: null
-description: Generate a native oprim capability spec delta at oprim/bets/BET-NNN-<slug>/specs/<capability>/spec.md while a bet is active, in RFC 2119 (SHALL/SHOULD/MAY) requirements and Gherkin scenarios — folded into oprim/specs/<capability>/spec.md (current truth) when the bet is archived
+description: Generate a native oprim capability spec delta at oprim/bets/pending/BET-NNN-<slug>/specs/<capability>/spec.md while a bet is active, in RFC 2119 (SHALL/SHOULD/MAY) requirements and Gherkin scenarios — folded into oprim/specs/<capability>/spec.md (current truth) when the bet is archived. On the first invocation for a bet, also generates design.md and tasks.md alongside the spec delta.
 claude:
   skill: true
   command: null

package/dist/workflows/spec-authoring.template.md

@@ -1,6 +1,6 @@
 ---
 name: oprim-spec
-description: Generate a native oprim capability spec delta at oprim/bets/BET-NNN-<slug>/specs/<capability>/spec.md while a bet is active, in RFC 2119 (SHALL/SHOULD/MAY) requirements and Gherkin scenarios — folded into oprim/specs/<capability>/spec.md (current truth) when the bet is archived
+description: Generate a native oprim capability spec delta at oprim/bets/pending/BET-NNN-<slug>/specs/<capability>/spec.md while a bet is active, in RFC 2119 (SHALL/SHOULD/MAY) requirements and Gherkin scenarios — folded into oprim/specs/<capability>/spec.md (current truth) when the bet is archived. On the first invocation for a bet, also generates design.md and tasks.md alongside the spec delta.
 ---
 
 Generate a capability spec delta for an active bet — RFC 2119 requirements plus Gherkin scenarios, no OpenSpec required. This skill never writes to `oprim/specs/` directly; `oprim-archive` folds the delta into current truth when the bet is archived.
@@ -12,14 +12,14 @@ Generate a capability spec delta for an active bet — RFC 2119 requirements plu
 ### 1. Get the active bet
 If a bet ID was provided as context (e.g. invoked from `/oprim:promote`), use it directly. Otherwise ask: "Which bet is this spec change for? (e.g. BET-005)"
 
-Resolve it to a directory in `oprim/bets/` using the same two patterns `oprim-archive` uses: exact `BET-NNN/` (legacy, no slug) or the slug variant `BET-NNN-<slug>/`. If neither matches, report "Bet BET-NNN was not found in oprim/bets/ — spec deltas can only be authored against an active bet" and stop.
+Resolve it to a directory in `oprim/bets/pending/` using the same two patterns `oprim-archive` uses: exact `BET-NNN/` (legacy, no slug) or the slug variant `BET-NNN-<slug>/`. If neither matches, report "Bet BET-NNN was not found in oprim/bets/pending/ — spec deltas can only be authored against an active bet" and stop.
 
 ### 2. Get the capability name and description
 If not provided, ask: "What capability are you specifying? (a short name, e.g. 'spec-authoring')" and "What does it do? (one or two sentences)"
 
 ### 2b. Derive the slug
 From the capability name: 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. This becomes `<capability>`.
-Output path: `oprim/bets/<resolved-bet-dir>/specs/<capability>/spec.md` (a delta, not `oprim/specs/<capability>/spec.md` — that file is current truth and is only ever written by `oprim-archive`'s merge step).
+Output path: `oprim/bets/pending/<resolved-bet-dir>/specs/<capability>/spec.md` (a delta, not `oprim/specs/<capability>/spec.md` — that file is current truth and is only ever written by `oprim-archive`'s merge step).
 
 ### 2c. Check for custom rules
 Read `oprim/config.yaml`. If it has a non-empty `rules.spec` value, treat it as additional guidance from the team — factor it into the requirements and scenarios you draft. If `rules.spec` is absent or empty, skip this step; behavior is unchanged.
@@ -33,8 +33,20 @@ For each requirement, ask whether it is new (**ADDED**), a change to an existing
 ### 4. Gather requirements and scenarios
 For ADDED and MODIFIED requirements, phrase each as an RFC 2119 statement using SHALL (mandatory), SHOULD (recommended), or MAY (optional), then ask for at least one scenario: a WHEN (trigger) and a THEN (expected outcome), with an optional GIVEN (context) and additional AND steps. REMOVED requirements only need the matching header — no new scenarios.
 
-### 5. Write the delta file
-Append to (or create) `oprim/bets/<resolved-bet-dir>/specs/<capability>/spec.md`, grouping requirements under the matching section header — only include a section if it has at least one requirement under it:
+### 5. Check for existing design/tasks artifacts
+Before writing the spec delta, check whether `design.md` and `tasks.md` already exist in `oprim/bets/pending/<resolved-bet-dir>/`.
+
+- If neither exists, this is the first `oprim-spec` invocation for this bet — continue to Step 6 to draft both before writing the delta.
+- If either already exists (from a prior `oprim-spec` invocation for this bet, e.g. for a different capability), skip Step 6 entirely and go straight to Step 7 — only the spec delta is written or appended.
+
+### 6. Draft design.md and tasks.md (first invocation only)
+Only performed when Step 5 found neither file yet exists. Write both to `oprim/bets/pending/<resolved-bet-dir>/`:
+
+1. **`design.md`** — the technical approach and trade-offs for the capability being specced: key decisions, alternatives considered, risks. Scope it to this capability's implementation, not the whole bet.
+2. **`tasks.md`** — a flat implementation checklist derived from the requirements and scenarios just captured in Step 4. Group tasks under `## N. <heading>` sections (one heading per logical unit of work, e.g. per requirement or component) with `- [ ] N.M <task description>` checkbox items beneath each — the same convention OpenSpec's own `tasks.md` uses, so completion is a simple parse (count of unchecked boxes), not a new format to learn.
+
+### 7. Write the delta file
+Append to (or create) `oprim/bets/pending/<resolved-bet-dir>/specs/<capability>/spec.md`, grouping requirements under the matching section header — only include a section if it has at least one requirement under it:
 
 ```markdown
 ## ADDED Requirements
@@ -64,5 +76,7 @@ Append to (or create) `oprim/bets/<resolved-bet-dir>/specs/<capability>/spec.md`
 
 If the delta file already exists (a prior spec-authoring pass for this bet/capability), append new requirements to the matching section, creating that section if it's not yet present.
 
-### 6. Report what was created
+### 8. Report what was created
 Show the delta file path, which bet it's scoped to, and a summary of the ADDED/MODIFIED/REMOVED requirements captured. Note that it merges into `oprim/specs/<capability>/spec.md` when `BET-NNN` is archived — nothing is current truth yet.
+
+On a first invocation (Step 6 ran), also report the `design.md` and `tasks.md` paths that were created. On a later invocation (Step 6 skipped), note that those two files already existed and were left untouched.

package/dist/workflows/tutorial.schema.yaml

@@ -0,0 +1,13 @@
+id: tutorial
+skillName: oprim-tutorial
+title: null
+description: Guided walkthrough of the oprim bet -> spec -> archive cycle inside the todo-app example workspace (examples/) -- creates a real "add due dates to tasks" bet, specs it, and archives it, narrating each step against the example's existing PDRs, bets, and current-truth specs
+claude:
+  skill: true
+  command: null
+cursor:
+  skill: true
+  command: null
+poolside:
+  skill: true
+inline: false

package/dist/workflows/tutorial.template.md

@@ -0,0 +1,45 @@
+---
+name: oprim-tutorial
+description: Guided walkthrough of the oprim bet -> spec -> archive cycle inside the todo-app example workspace (examples/) -- creates a real "add due dates to tasks" bet, specs it, and archives it, narrating each step against the example's existing PDRs, bets, and current-truth specs
+---
+
+Walk the user through one full oprim workflow cycle — bet → spec → archive — inside this example workspace, using a real new feature for the mock todo app: **"Add due dates to tasks."** This is not a simulation: it invokes the same `oprim-bet`, `oprim-spec`, and `oprim-archive` skills a real project uses, against this workspace's real files.
+
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question you ask directly. When a step delegates to another skill via the Skill tool, that skill drives its own prompts.
+
+## Before you start
+
+Orient the user in 2-3 sentences before Step 1:
+- This workspace (`oprim/`) already has a working example: `PDR-001`/`PDR-002` record two early product decisions, `BET-001` (archived) shipped the core add/complete/delete loop, and `oprim/specs/task-management/spec.md` is that feature's current-truth spec. `BET-002` (pending) is a backlog idea for later.
+- This tutorial adds a new bet on top of that foundation — due dates — and carries it all the way through the cycle: bet decision → spec delta → archive.
+
+## Steps
+
+### 1. Create the bet
+Invoke the **`oprim-bet`** skill using the Skill tool. Suggest (but do not force) the title **"Add due dates to tasks"** if the user doesn't already have one in mind, and note that PDR-001 (flat lists) and PDR-002 (local-only storage) are the relevant prior decisions to link.
+
+After the skill finishes, confirm the new bet's ID (it will be the next available `BET-NNN` — `BET-003` if this is the first tutorial run) and its directory under `oprim/bets/pending/`.
+
+### 2. Author the spec delta
+Invoke the **`oprim-spec`** skill using the Skill tool, passing the bet ID from Step 1. When it asks for a capability name, suggest **"task-management"** — the same capability `BET-001` shipped — since due dates extend that existing surface rather than introducing a new one. When it asks whether each requirement is ADDED/MODIFIED/REMOVED, this is an ADDED requirement (due dates are new, nothing existing changes).
+
+This also scaffolds `design.md` and `tasks.md` for the bet (first `oprim-spec` invocation for a bet always does). Point the user at both files afterward.
+
+### 3. Note the pre-archive state
+Before archiving, briefly show the user what's about to change:
+- `oprim/bets/pending/BET-NNN-.../` will move to `oprim/bets/archived/`
+- The new ADDED requirement(s) will be appended to the existing `oprim/specs/task-management/spec.md` (current truth), alongside the three requirements `BET-001` already put there
+- The bet's entry will be removed from `oprim/sequence.yaml`
+
+This is the same fold `/oprim:archive` performs on any real project — nothing tutorial-specific happens here.
+
+### 4. Archive the bet
+Invoke the **`oprim-archive`** skill using the Skill tool, passing the bet ID from Step 1. Let it run its normal checks (dependents, delta overlaps, incomplete `tasks.md`) — if `tasks.md` still has unchecked items, that's expected for a fresh tutorial run; the user can confirm through the warning or check off items first.
+
+### 5. Show the result
+Report what changed, pointing at real file paths:
+- `oprim/bets/archived/BET-NNN-.../` — the completed bet, in full
+- `oprim/specs/task-management/spec.md` — now includes the due-date requirement(s) alongside `BET-001`'s original three
+- `oprim/sequence.yaml` — no longer lists `BET-NNN`
+
+Close by telling the user they just completed a full oprim cycle — the same one this tool uses on itself (see this repository's own `oprim/` workspace) — and that running it again works identically on their own project after `oprim init`.

package/package.json

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