@open-product-primer/cli 2.3.0 → 2.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
id: tutorial
|
|
2
|
+
skillName: oprim-tutorial
|
|
3
|
+
title: null
|
|
4
|
+
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
|
|
5
|
+
claude:
|
|
6
|
+
skill: true
|
|
7
|
+
command: null
|
|
8
|
+
cursor:
|
|
9
|
+
skill: true
|
|
10
|
+
command: null
|
|
11
|
+
poolside:
|
|
12
|
+
skill: true
|
|
13
|
+
inline: false
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: oprim-tutorial
|
|
3
|
+
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
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
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.
|
|
7
|
+
|
|
8
|
+
**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.
|
|
9
|
+
|
|
10
|
+
## Before you start
|
|
11
|
+
|
|
12
|
+
Orient the user in 2-3 sentences before Step 1:
|
|
13
|
+
- 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.
|
|
14
|
+
- 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.
|
|
15
|
+
|
|
16
|
+
## Steps
|
|
17
|
+
|
|
18
|
+
### 1. Create the bet
|
|
19
|
+
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.
|
|
20
|
+
|
|
21
|
+
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/`.
|
|
22
|
+
|
|
23
|
+
### 2. Author the spec delta
|
|
24
|
+
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).
|
|
25
|
+
|
|
26
|
+
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.
|
|
27
|
+
|
|
28
|
+
### 3. Note the pre-archive state
|
|
29
|
+
Before archiving, briefly show the user what's about to change:
|
|
30
|
+
- `oprim/bets/pending/BET-NNN-.../` will move to `oprim/bets/archived/`
|
|
31
|
+
- 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
|
|
32
|
+
- The bet's entry will be removed from `oprim/sequence.yaml`
|
|
33
|
+
|
|
34
|
+
This is the same fold `/oprim:archive` performs on any real project — nothing tutorial-specific happens here.
|
|
35
|
+
|
|
36
|
+
### 4. Archive the bet
|
|
37
|
+
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.
|
|
38
|
+
|
|
39
|
+
### 5. Show the result
|
|
40
|
+
Report what changed, pointing at real file paths:
|
|
41
|
+
- `oprim/bets/archived/BET-NNN-.../` — the completed bet, in full
|
|
42
|
+
- `oprim/specs/task-management/spec.md` — now includes the due-date requirement(s) alongside `BET-001`'s original three
|
|
43
|
+
- `oprim/sequence.yaml` — no longer lists `BET-NNN`
|
|
44
|
+
|
|
45
|
+
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`.
|