@open-product-primer/cli 2.1.0 → 2.2.0

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

package/dist/workflows/review.template.md

@@ -0,0 +1,69 @@
+---
+name: oprim-review
+description: Create a KPI review artifact for a completed bet, pre-filled from criteria.yaml with actuals gathered from the user
+---
+
+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
+If not provided, ask: "Which bet are you reviewing? (e.g. BET-042)"
+
+### 1b. Check for custom rules
+Read `oprim/config.yaml`. If it has a non-empty `rules.review` 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 review content. If `rules.review` is absent or empty, skip this step; behavior is unchanged.
+
+### 2. Load criteria and check for a run result
+
+Read `oprim/bets/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.
+
+**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.
+
+**If no run result exists:** proceed to step 3 to gather actuals manually.
+
+### 3. Gather actuals per metric (only when no run result)
+For each metric show name/baseline/target and ask: "What was the actual result? (number or 'pending')"
+
+Status logic:
+- actual >= target → `hit`
+- actual < target → `missed`
+- 'pending' or not provided → `pending`
+
+### 4. Get review metadata
+Ask: reviewer name, decision quality notes.
+
+### 5. Output path
+`oprim/reviews/YYYY-MM-DD-BET-NNN-kpi.md` (today's date)
+
+### 5b. Check for OKF frontmatter
+Read `oprim/templates/kpi-review.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 (derived from the reviewed bet's subject area). Prepare a frontmatter block with `type: kpi-review`, `title: <bet ID and title>`, `description: <description>`, `tags: [<tags>]`, `timestamp: <review date, ISO 8601>`, to prepend in step 6.
+If no frontmatter block is found in the template, skip this step — write the file with no frontmatter, matching current behavior.
+
+### 6. Write the review file
+Prepend the frontmatter block from step 5b, if one was prepared.
+```markdown
+# KPI Review: BET-NNN
+
+**Review date:** YYYY-MM-DD
+**Reviewed by:** <reviewer>
+**Actuals from run:** YYYY-MM-DD  ← include only when a run result was ingested
+
+| Metric | Baseline | Target | Actual | Status |
+|--------|----------|--------|--------|--------|
+| <name> | <baseline> | <target> | <actual> | <status> |
+
+## Decision quality
+<notes>
+
+## Actions
+- [ ] Update bet-decision outcome section
+- [ ] Update affected PDRs
+- [ ] Re-sequence impacted bets
+```
+
+### 7. Report what was created

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

@@ -0,0 +1,12 @@
+
+Validate the primer sequencing board and suggest rebalancing if needed.
+
+**Steps**
+
+1. **Read board** — load `oprim/sequence.yaml`
+2. **Check WIP limits** — compare `now` count against `wip_limits.now`
+3. **Validate blockers** — for each bet in `now`, confirm all `blocked_by` entries are complete or absent
+4. **Validate PDR preconditions** — confirm all `requires_pdrs` entries exist in `oprim/decisions/`
+5. **Report violations** — list any WIP excess, unresolved blockers, or missing PDRs
+6. **Suggest moves** — recommend bets to defer to `next` or `later` to resolve violations
+7. **Regenerate view** — run `node oprim/scripts/generate-sequence-view.js` from the project root to update `oprim/sequence-view.md`

package/dist/workflows/sequence.inline.md

@@ -0,0 +1,10 @@
+### Sequencing board (oprim-sequence)
+Validate the primer sequencing board and regenerate the visual view.
+
+1. **Read board** — load `oprim/sequence.yaml`
+2. **Check WIP limits** — compare `now` count against `wip_limits.now`
+3. **Validate blockers** — for each bet in `now`, confirm all `blocked_by` entries are complete or absent
+4. **Validate PDR preconditions** — confirm all `requires_pdrs` entries exist in `oprim/decisions/`
+5. **Report violations** — list any WIP excess, unresolved blockers, or missing PDRs
+6. **Suggest moves** — recommend bets to defer to `next` or `later` to resolve violations
+7. **Regenerate view** — run `node oprim/scripts/generate-sequence-view.js` from the project root to update `oprim/sequence-view.md`

package/dist/workflows/sequence.schema.yaml

@@ -0,0 +1,13 @@
+id: sequence
+skillName: oprim-sequence
+title: "OPRIM: Sequence"
+description: Validate and update the primer sequencing board
+claude:
+  skill: true
+  command: sequence.md
+cursor:
+  skill: false
+  command: oprim-sequence.md
+poolside:
+  skill: true
+inline: true

package/dist/workflows/sequence.template.md

@@ -0,0 +1,88 @@
+---
+name: oprim-sequence
+description: Validate and update the primer sequencing board — triage mode computes board health and surfaces specific suggestions; seeded mode targets a specific context
+---
+
+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.
+**Seeded mode** — context pre-provided (e.g. from a lifecycle hook): skips full triage and targets the most relevant move for that context.
+
+## Steps
+
+### 1. Determine mode
+
+If lifecycle context was provided as an argument or pre-seeded in the conversation (e.g. `bet-created`, `bet-promoted`, or a specific bet ID was just archived), enter **Seeded mode** — go to Step 2B.
+
+Otherwise, enter **Triage mode** — go to Step 2A.
+
+### 2A. Triage mode — compute board health
+
+Read `oprim/sequence.yaml`. Compute:
+
+- **WIP utilization**: count entries in `now` vs `wip_limits.now`
+- **WIP violations**: entries in `now` that exceed the WIP limit
+- **Blocked Now bets**: entries in `now` whose `blocked_by` list contains a bet ID still present in any active lane (now/next/later/backlog)
+- **Ready-to-pull bets**: entries in `next` whose `blocked_by` list is empty or all resolved (each blocked_by ID is absent from all active lanes)
+- **PDR gaps**: entries in any lane whose `requires_pdrs` list contains a PDR ID not found in `oprim/decisions/`
+
+Surface **ranked suggestions**, most urgent first:
+1. WIP violations → name each excess bet, suggest deferring to `next` or `later`
+2. Blocked Now bets → name the bet and its unresolved blocker, suggest deferring until blocker resolves
+3. Open Now slot (count < `wip_limits.now`) with a ready Next bet → name a specific bet to pull into `now`
+4. PDR gaps → name the bet and missing PDR, suggest creating it first
+
+Each suggestion must name the exact bet ID, current lane, target lane, and reason.
+
+If the board is healthy (no violations, no ready moves): report current WIP utilization and state the board is healthy. Offer to move something anyway if the user wants.
+
+After surfacing suggestions, ask: "Which move would you like to make?"
+
+### 2B. Seeded mode — target specific context
+
+Use the provided context to jump to the most relevant suggestion:
+
+- `bet-created`: A new bet just landed in backlog. Check if `now` has an open slot and `next` has a ready bet to pull. If so, suggest the specific bet to pull. Otherwise, confirm the new bet is in backlog and the board looks healthy.
+- `bet-promoted`: A bet was just promoted to an OpenSpec change. Verify the bet is still correctly sequenced and surface any resequencing action the promotion warrants.
+- Bet archived (e.g. "BET-011 was archived"): Check if `now` dropped below `wip_limits.now`. If so, find the most ready bet in `next` and suggest pulling it.
+
+If no relevant move is found for the provided context, fall back to Triage mode (Step 2A).
+
+### 3. Validate the requested move
+
+Before executing any move, verify all three constraints:
+
+**WIP limit**: Moving a bet to `now` must not push the count above `wip_limits.now`. If it would, explain the violation and suggest deferring an existing `now` bet first.
+
+**Blocker resolution**: Moving a bet to `now` requires its `blocked_by` list to be empty or all resolved (IDs absent from all active lanes). If unresolved, name each unresolved blocker.
+
+**PDR preconditions**: Moving a bet to `now` requires all `requires_pdrs` entries to exist as files in `oprim/decisions/`. If any are missing, name them and suggest creating them first.
+
+If the move is invalid: explain which constraint failed and suggest the nearest valid alternative. Do not proceed to Step 4.
+
+### 4. Preview and confirm
+
+Show the exact YAML change before writing. Name the entry that will move: its `id`, `title`, source lane, and target lane.
+
+```
+Before:  BET-005 is in next  (now: 1/2 slots filled)
+After:   BET-005 moves to now (now: 2/2 slots filled)
+```
+
+Ask: "Apply this change? (y/N)"
+- If "n" or Enter: stop, no changes made.
+- If "y": proceed to Step 5.
+
+### 5. Write sequence.yaml
+
+Read `oprim/sequence.yaml`. Remove the bet entry from its current lane. Insert it into the target lane. Write back with 2-space indentation. Do not modify any other entries.
+
+### 6. Regenerate view
+
+Run `node oprim/scripts/generate-sequence-view.js` from the project root to update `oprim/sequence-view.md`.
+
+### 7. Report what was done

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

@@ -0,0 +1,13 @@
+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
+claude:
+  skill: true
+  command: null
+cursor:
+  skill: true
+  command: null
+poolside:
+  skill: true
+inline: false

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

@@ -0,0 +1,68 @@
+---
+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
+---
+
+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.
+
+**Interactive prompts:** Use the **AskUserQuestion tool** for every question in this skill — do not write questions as plain text.
+
+## Steps
+
+### 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.
+
+### 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).
+
+### 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.
+
+### 3. Determine the delta type for each requirement
+For each requirement, ask whether it is new (**ADDED**), a change to an existing current-truth requirement (**MODIFIED**), or a removal of one (**REMOVED**).
+
+- **ADDED**: gather the requirement statement fresh.
+- **MODIFIED / REMOVED**: read `oprim/specs/<capability>/spec.md` if it exists and list its `### Requirement:` headers so the user can pick the one being changed. The header text must match exactly (whitespace-insensitive) for `oprim-archive`'s merge step to find it later. If the file doesn't exist yet, MODIFIED/REMOVED aren't possible for this capability — fall back to ADDED.
+
+### 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:
+
+```markdown
+## ADDED Requirements
+
+### Requirement: <capability> SHALL/SHOULD/MAY <requirement statement>
+<one-sentence elaboration>
+
+#### Scenario: <scenario title>
+- **GIVEN** <context> (optional)
+- **WHEN** <trigger>
+- **THEN** <outcome>
+- **AND** <additional outcome> (optional)
+
+## MODIFIED Requirements
+
+### Requirement: <exact header text matched from oprim/specs/<capability>/spec.md>
+<revised elaboration>
+
+#### Scenario: <scenario title>
+- **WHEN** <trigger>
+- **THEN** <outcome>
+
+## REMOVED Requirements
+
+### Requirement: <exact header text matched from oprim/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
+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.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@open-product-primer/cli",
-  "version": "2.1.0",
+  "version": "2.2.0",
   "description": "Open Product Primer CLI — product decisions, sequencing, and KPI tracking for repositories",
   "keywords": [
     "product",
@@ -35,7 +35,7 @@
     "README.md"
   ],
   "scripts": {
-    "build": "tsc",
+    "build": "tsc && node scripts/copy-workflow-assets.js",
     "dev": "tsc --watch",
     "start": "node dist/cli.js",
     "test": "vitest run",