@open-product-primer/cli 2.0.0 → 2.2.0

package/dist/workflows/bet.template.md

@@ -0,0 +1,114 @@
+---
+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
+---
+
+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
+Display the naming convention before asking:
+
+> **Naming tip:** Use "verb + object [for context]"
+> - Good: "Improve bet naming for scannability"
+> - Bad: "Naming"
+
+If not provided, ask: "What is the title of this bet?"
+
+After receiving the title, validate: if fewer than 4 words OR fewer than 25 characters:
+- Show: "Warning: this title may be too vague to scan at a glance."
+- Suggest a reformulation, e.g. "Consider: 'Improve <what> for <why>'"
+- Ask: "Proceed with this title anyway? (y/N)"
+  - If "n" or Enter: ask for a revised title and re-validate
+  - 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.
+
+### 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`.
+
+### 3b. Check for custom rules
+Read `oprim/config.yaml`. If it has a non-empty `rules.bet` value, treat it as additional guidance from the team — factor it into the questions you ask in step 4 and reflect it in the generated `bet-decision.md` content. If `rules.bet` is absent or empty, skip this step; behavior is unchanged.
+
+### 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).
+
+Then ask about reversibility:
+- "Is this a **2-way door** (reversible — easy to undo, safe to try) or a **1-way door** (hard to reverse — requires high confidence)?"
+
+Then ask about each of the four risk dimensions (Low / Medium / High + short rationale):
+- "**Value risk**: Will users/customers actually use or buy this? (Low / Medium / High — and why?)"
+- "**Usability risk**: Can users figure out how to use it without help? (Low / Medium / High — and why?)"
+- "**Feasibility risk**: Can we build this with our current skills, time, and technology? (Low / Medium / High — and why?)"
+- "**Business viability risk**: Does this solution work for the business (revenue, legal, ops)? (Low / Medium / High — and why?)"
+
+### 4b. Check for OKF frontmatter
+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
+Prepend the frontmatter block from step 4b, if one was prepared.
+```
+# Decision: BET-NNN <title>
+<!-- Naming tip: verb + object [for context] — e.g. "Improve bet naming for scannability" not "Naming" -->
+
+## Status
+- Decision: <decision>
+- Date: <today YYYY-MM-DD>
+- Owner: <owner>
+- Review date: <review date>
+
+## Door type
+- [<x if 2-way>] 2-way door (reversible — safe to try, easy to undo)
+- [<x if 1-way>] 1-way door (hard to reverse — requires higher confidence before committing)
+
+## Risk profile
+- **Value risk**: <Low / Medium / High> — <rationale>
+- **Usability risk**: <Low / Medium / High> — <rationale>
+- **Feasibility risk**: <Low / Medium / High> — <rationale>
+- **Business viability risk**: <Low / Medium / High> — <rationale>
+
+## Why now
+<why-now as bullet list>
+
+## Alternatives considered
+<alternatives as bullet list>
+
+## Expected outcomes
+<outcomes as bullet list>
+
+## Kill criteria / rollback trigger
+<kill criteria as bullet list>
+
+## Links
+- PDRs: <PDR-IDs or "None">
+- OpenSpec change: <to be filled when promoted>
+```
+
+### 6. Append to oprim/sequence.yaml backlog
+Read → parse YAML → append → write back (2-space indentation):
+```yaml
+- id: BET-NNN
+  title: "<title>"
+  blocked_by: []
+  unlocks: []
+  requires_pdrs: []
+```
+
+### 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 "n" or Enter: skip silently.
+
+### 8. Report what was created

package/dist/workflows/context.schema.yaml

@@ -0,0 +1,13 @@
+id: context
+skillName: oprim-context-init
+title: "OPRIM: Context Init"
+description: Declare the current project a citable remote context, guided by a short Q&A to draft its description
+claude:
+  skill: true
+  command: context-init.md
+cursor:
+  skill: false
+  command: null
+poolside:
+  skill: false
+inline: false

package/dist/workflows/context.template.md

@@ -0,0 +1,34 @@
+---
+name: oprim-context-init
+description: Guide the user through drafting a description before declaring the current project a citable remote context
+---
+
+Declare the current project a citable remote context, with a clear description other projects and agents can use to decide whether to pull it.
+
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
+
+## What this does
+
+A remote context is an oprim workspace (decisions, bets, specs) that other projects can reference read-only via `oprim context register`. Without a description, other projects have no cheap way to know what a remote context covers short of fully pulling it — so this skill exists to make sure one gets written.
+
+## Steps
+
+### 1. Check for an existing identity
+Check whether `.oprim-context/context.yaml` already exists in the current project. If it does, report that a remote context identity already exists (do not re-run the drafting flow below) and stop.
+
+### 2. Ask what this workspace covers
+Ask the user, one at a time:
+- "What does this project's oprim workspace cover? (e.g. product decisions, a specific domain, a team's specs)"
+- "Who is this meant for — which teams or projects would reference it?"
+
+If the user declines to answer either question, treat that as opting out of guided drafting — skip to step 4 with no description.
+
+### 3. Draft and confirm the description
+From the answers, draft a single-sentence description (aim for under 120 characters — this is what `oprim context list` will show other projects). Show the draft to the user and ask: "Use this description? (Enter to accept, or type a replacement)"
+
+### 4. Call oprim context init
+- If a description was drafted or accepted: use the Bash tool to run `oprim context init --description "<final text>"`.
+- If the user opted out in step 2: warn clearly that the resulting remote context will show as description-less in `oprim context list`, then use the Bash tool to run `oprim context init` with no `--description` flag.
+
+### 5. Report what was created
+Report the path (`.oprim-context/context.yaml`) and the description that was set (or the description-less warning, if opted out).

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

@@ -0,0 +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.

package/dist/workflows/criteria.inline.md

@@ -0,0 +1,11 @@
+### Criteria authoring (oprim-criteria)
+Create or append to `oprim/bets/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.
+3. Ask source type (amplitude / bigquery).
+   - Amplitude: event, aggregation (unique_users/event_count/property_sum), denominator_event.
+   - BigQuery: table, metric_column, filter, aggregation, denominator_query.
+4. If file exists: append to `metrics` list (never overwrite). If not: create.
+5. Ask if adding more metrics.
+6. Report what was created.

package/dist/workflows/criteria.schema.yaml

@@ -0,0 +1,14 @@
+id: criteria
+skillName: oprim-criteria
+title: null
+description: Create or append to a criteria.yaml contract for a bet, with structured Amplitude and BigQuery source mapping
+cursorDescription: Create or append to a criteria.yaml contract for a bet
+claude:
+  skill: true
+  command: null
+cursor:
+  skill: true
+  command: oprim-criteria.md
+poolside:
+  skill: true
+inline: true

package/dist/workflows/criteria.template.md

@@ -0,0 +1,52 @@
+---
+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`.
+
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
+
+## Steps
+
+### 1. Identify the bet
+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.
+
+### 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).
+
+### 4. Gather source mapping
+Ask: source type (amplitude / bigquery)
+
+If amplitude: event name, aggregation (unique_users / event_count / property_sum), denominator event (optional).
+```yaml
+source:
+  type: amplitude
+  definition:
+    event: <event_name>
+    aggregation: <aggregation>
+    denominator_event: <event_name | null>
+```
+
+If bigquery: table, metric column, SQL filter, aggregation (sum / count / count_distinct / avg), denominator query (optional).
+```yaml
+source:
+  type: bigquery
+  definition:
+    table: "<project.dataset.table>"
+    metric_column: "<column>"
+    filter: "<sql_filter>"
+    aggregation: <aggregation>
+    denominator_query: <sql | null>
+```
+
+### 5. Build metric entry and write
+If file exists: read → parse → append to `metrics` → write back (never overwrite).
+If not: create with `metrics:` list.
+
+### 6. Ask if more metrics needed. If yes, return to step 3.
+
+### 7. Report what was created

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

@@ -0,0 +1 @@
+Create a new note in `oprim/notes/` for lightweight thinking capture — an observation, idea, or connection that hasn't yet earned a place in a bet or PDR. Notes carry no owner or kill criterion; promote one into a bet later with `/oprim:promote NOTE-NNN`. Ask for a short title. Scan `oprim/notes/NOTE-(\d+)-` for the next id (zero-padded, default 001). Ask for the note body (free-form), tags, and optional related BET-IDs. Tags are checked against `oprim/config.yaml`'s `notes.tags`; any new tag is accepted and appended to that list rather than rejected — the vocabulary grows from usage. Read `oprim/templates/note.md` — if its frontmatter has a `description:` field, this workspace is on the OKF tier and needs a one-line description; if it has no `description:` field, use the minimal tier; if the file doesn't exist, fall back to reading `okf.enabled` directly from `oprim/config.yaml`. Write `oprim/notes/NOTE-NNN-<slug>.md` with the correct frontmatter tier and a `## Bets` section listing any related BET-IDs. For each related bet, append `- Notes: NOTE-NNN` to that bet-decision's `## Links` section. Report what was created.

package/dist/workflows/note.inline.md

@@ -0,0 +1,11 @@
+### Note authoring (oprim-note)
+Create a new note in `oprim/notes/` for lightweight thinking capture — not a bet, no owner or kill criterion.
+
+1. Ask for a short title.
+2. Assign next NOTE ID: scan `oprim/notes/NOTE-(\d+)-`, max+1 zero-padded to 3 digits (default 001).
+3. Ask for the note body (free-form), tags, and optional related BET-IDs.
+4. Tags: check against `oprim/config.yaml`'s `notes.tags` — accept and append any new tag rather than rejecting it (the vocabulary grows from usage).
+5. Check `oprim/templates/note.md`: a `description:` field in its frontmatter means the OKF tier (gather a one-line description); no field means the minimal tier; if the file is missing, fall back to `okf.enabled` in `oprim/config.yaml`.
+6. Write `oprim/notes/NOTE-NNN-<slug>.md` with the correct frontmatter tier and a `## Bets` section.
+7. For each related bet, append `- Notes: NOTE-NNN` to that bet's `## Links` section.
+8. Report what was created.

package/dist/workflows/note.schema.yaml

@@ -0,0 +1,14 @@
+id: note
+skillName: oprim-note
+title: null
+description: Create a new atomic note in oprim/notes/ for lightweight thinking capture, with tiered frontmatter and optional bet links
+cursorDescription: Create a new atomic note for lightweight thinking capture
+claude:
+  skill: true
+  command: null
+cursor:
+  skill: true
+  command: oprim-note.md
+poolside:
+  skill: true
+inline: true

package/dist/workflows/note.template.md

@@ -0,0 +1,66 @@
+---
+name: oprim-note
+description: Create a new atomic note in oprim/notes/ for lightweight thinking capture, with tiered frontmatter and optional bet links
+---
+
+Create a new note in `oprim/notes/` for lightweight thinking capture — an observation, idea, or connection that hasn't yet earned a place in a bet or PDR.
+
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
+
+## What you're creating
+
+A note is a small, disposable unit of thinking: an observation, a stray idea, or a connection between bets, captured before it's proven enough to belong in a discovery hypothesis or bet-decision. Notes carry no owner and no kill criterion — they're not commitments. Promote a note into a bet later with `/oprim:promote NOTE-NNN` once it's worth committing to.
+
+## Steps
+
+### 1. Get the note title
+If not provided, ask: "What is this note about? (a short title)"
+
+### 2. Assign the next NOTE ID
+Scan `oprim/notes/` for files matching `NOTE-(\d+)-`. Extract the numeric part from each match. Assign max+1, zero-padded to 3 digits. Default `001` if none found.
+
+### 2b. Derive the slug
+From the note 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>`.
+Output path: `oprim/notes/NOTE-NNN-<slug>.md`
+
+### 3. Gather the note body
+Ask: "What's the observation, idea, or connection?" (free-form prose — this becomes the note body).
+
+### 4. Gather tags
+Read `oprim/config.yaml`. If it has a `notes:` section with a `tags:` list, show it and ask the user to pick from it or add new ones. If `notes.tags` is absent or empty, ask for tags directly (comma-separated) — there's no vocabulary yet to constrain against.
+A tag not already in `notes.tags` SHALL be accepted, never rejected, and appended to `oprim/config.yaml`'s `notes.tags` list (creating the `notes:` section if absent) — the vocabulary grows from usage rather than requiring upfront authoring.
+
+### 5. Gather optional bet links
+Ask: "Does this relate to any existing bets? (comma-separated BET-IDs, or Enter to skip)"
+
+### 6. Check the frontmatter tier
+Read `oprim/templates/note.md`.
+- If it exists and its frontmatter block contains a `description:` field, this workspace is on the **OKF tier** — ask for a one-line description.
+- If it exists with no `description:` field, use the **minimal tier** — skip the description.
+- If the file doesn't exist (project initialized before notes were introduced), read `oprim/config.yaml` directly: `okf.enabled: true` → OKF tier (ask for a description); otherwise → minimal tier.
+
+### 7. Write oprim/notes/NOTE-NNN-<slug>.md
+
+Minimal tier:
+```
+---
+type: note
+title: "<title>"
+tags: [<tags>]
+timestamp: <today, ISO 8601>
+---
+
+# Note: <title>
+
+<body>
+
+## Bets
+- <BET-IDs from step 5, or "None">
+```
+
+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).
+
+### 9. Report what was created

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

@@ -0,0 +1 @@
+Create a new PDR in `oprim/decisions/`. Scan for `PDR-(\d+)-` to assign next ID (zero-padded, default 001). Read `oprim/config.yaml`'s `rules.pdr` — if non-empty, apply it as additional guidance and reflect it in the generated content; if empty, behavior is unchanged. 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.

package/dist/workflows/pdr.inline.md

@@ -0,0 +1,10 @@
+### PDR authoring (oprim-pdr)
+Create a new Product Decision Record in `oprim/decisions/`.
+
+1. Ask for decision title.
+2. Assign next PDR ID: scan `oprim/decisions/PDR-(\d+)-`, max+1 zero-padded to 3 digits (default 001).
+2b. Read `oprim/config.yaml`'s `rules.pdr` — if non-empty, apply it as additional guidance and reflect it in the generated content; if empty, behavior is unchanged.
+3. Gather: context, decision, alternatives, consequences, evidence, related bets/specs.
+4. Ask if superseding an existing PDR.
+5. Write `oprim/decisions/PDR-NNN-<slug>.md`. If superseding, update old PDR Status.
+6. Report what was created.

package/dist/workflows/pdr.schema.yaml

@@ -0,0 +1,14 @@
+id: pdr
+skillName: oprim-pdr
+title: null
+description: Create a new Product Decision Record in oprim/decisions/ with auto-assigned ID and guided prompting
+cursorDescription: Create a new Product Decision Record with auto-assigned ID
+claude:
+  skill: true
+  command: null
+cursor:
+  skill: true
+  command: oprim-pdr.md
+poolside:
+  skill: true
+inline: true

package/dist/workflows/pdr.template.md

@@ -0,0 +1,67 @@
+---
+name: oprim-pdr
+description: Create a new Product Decision Record in oprim/decisions/ with auto-assigned ID and guided prompting
+---
+
+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
+If not provided, ask: "What is the title of this product decision?"
+
+### 2. Assign the next PDR ID
+Scan `oprim/decisions/` for files matching `PDR-(\d+)-`. Extract all integers. Assign max+1, zero-padded to 3 digits. Default `001` if none found.
+Slug: title → lowercase → spaces to hyphens → remove non-alphanumeric (except hyphens).
+Output path: `oprim/decisions/PDR-NNN-<slug>.md`
+
+### 2b. Check for custom rules
+Read `oprim/config.yaml`. If it has a non-empty `rules.pdr` value, treat it as additional guidance from the team — factor it into the questions you ask in step 3 and reflect it in the generated content. If `rules.pdr` is absent or empty, skip this step; behavior is unchanged.
+
+### 3. Gather content
+Ask: Context (what forced this decision), Decision (clear statement), Alternatives considered (why rejected), Consequences (positives / trade-offs / follow-ups), Evidence links (optional), Related bets (optional), Related OpenSpec changes (optional).
+
+### 4. Check for supersession
+Ask: "Does this supersede an existing PDR? If so, which ID? (Enter to skip)"
+
+### 4b. Check for OKF frontmatter
+Read `oprim/templates/pdr.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: pdr`, `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 the PDR file
+Prepend the frontmatter block from step 4b, if one was prepared.
+```
+# PDR-NNN: <title>
+
+## Status
+Proposed
+
+## Context
+<context>
+
+## Decision
+<decision>
+
+## Alternatives considered
+<alternatives as bullet list>
+
+## Consequences
+- Positive: <...>
+- Trade-offs: <...>
+- Follow-ups: <...>
+
+## Evidence
+<evidence or "None">
+
+## Related
+- Bets: <BET-IDs or "None">
+- OpenSpec: <change paths or "None">
+- Supersedes: <PDR-ID or "None">
+```
+
+### 6. Update superseded PDR (if applicable)
+Read the superseded file → replace Status value with `Superseded by PDR-NNN` → write back.
+
+### 7. Report what was created

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

@@ -0,0 +1,29 @@
+
+Promote an atomic note into a bet, or a prioritized bet into a capability spec. The promotion path is determined solely by the prefix of the ID argument — there is no separate command for each.
+
+**Input**: Specify an ID (e.g., `/oprim:promote BET-042` or `/oprim:promote NOTE-005`) or omit to be prompted.
+
+### 0. Determine the promotion path from the ID prefix
+- `BET-` → **A. Bet → native oprim spec**
+- `NOTE-` → **B. Note → Bet**
+- Anything else → report "Unrecognized ID prefix — expected BET- or NOTE-" and stop. Do not silently do nothing.
+
+## A. Bet → native oprim spec
+
+1. **Locate the bet** — read `oprim/bets/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
+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
+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.
+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

@@ -0,0 +1,25 @@
+
+Promote an atomic note into a bet, or a prioritized bet into a capability spec. The promotion path is determined solely by the prefix of the ID argument — there is no separate command for each.
+
+**Input**: Specify an ID (e.g., `/oprim:promote BET-042` or `/oprim:promote NOTE-005`) or omit to be prompted.
+
+### 0. Determine the promotion path from the ID prefix
+- `BET-` → **A. Bet → spec (no framework configured)**
+- `NOTE-` → **B. Note → Bet**
+- Anything else → report "Unrecognized ID prefix — expected BET- or NOTE-" and stop. Do not silently do nothing.
+
+## A. Bet → spec (no framework configured)
+
+1. **Locate the bet** — read `oprim/bets/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
+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.
+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

@@ -0,0 +1,40 @@
+
+Promote an atomic note into a bet, or a prioritized bet into a capability spec. The promotion path is determined solely by the prefix of the ID argument — there is no separate command for each.
+
+**Input**: Specify an ID (e.g., `/oprim:promote BET-042` or `/oprim:promote NOTE-005`) or omit to be prompted.
+
+### 0. Determine the promotion path from the ID prefix
+- `BET-` → **A. Bet → OpenSpec change**
+- `NOTE-` → **B. Note → Bet**
+- Anything else → report "Unrecognized ID prefix — expected BET- or NOTE-" and stop. Do not silently do nothing.
+
+## A. Bet → OpenSpec change
+
+1. **Locate the bet** — read `oprim/bets/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`.
+   - Pass the bet decision content as context so the proposal reflects the bet's why/outcome
+   - **Do not manually create a partial change directory** — the propose skill ensures no artifact is omitted
+   - The spec file(s) are mandatory: each capability modified or added must have WHEN/THEN scenarios under `## ADDED Requirements` or `## MODIFIED Requirements`
+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
+7. **Verify completeness** — confirm the change directory contains:
+   - `proposal.md`
+   - `design.md`
+   - `tasks.md`
+   - `specs/<capability>/spec.md` for each capability in `## Capabilities`
+   If any artifact is missing, create it before reporting done.
+8. **Report** — show what was linked and what remains for engineering
+
+## 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
+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.
+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.schema.yaml

@@ -0,0 +1,14 @@
+id: promote
+skillName: null
+title: "OPRIM: Promote"
+description: Promote a note into a bet, or a prioritized bet into a capability spec
+claude:
+  skill: false
+  command: promote.md
+cursor:
+  skill: false
+  command: oprim-promote.md
+poolside:
+  skill: false
+inline: false
+variants: [openspec, native, none]

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

@@ -0,0 +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.

package/dist/workflows/review.inline.md

@@ -0,0 +1,11 @@
+### KPI review (oprim-review)
+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.
+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.
+6. Write `oprim/reviews/YYYY-MM-DD-BET-NNN-kpi.md`.
+7. Report what was created.

package/dist/workflows/review.schema.yaml

@@ -0,0 +1,14 @@
+id: review
+skillName: oprim-review
+title: null
+description: Create a KPI review artifact for a completed bet, pre-filled from criteria.yaml with actuals gathered from the user
+cursorDescription: Create a KPI review artifact pre-filled from a bet's criteria contract
+claude:
+  skill: true
+  command: null
+cursor:
+  skill: true
+  command: oprim-review.md
+poolside:
+  skill: true
+inline: true