openrig-user

Name: openrig-user
Author: mvschwarz

56stars9forks

How to install openrig-user?

mvschwarz/openrig/openrig-user

$npx -y skills add mvschwarz/openrig --skill openrig-user

Installs into the current project.

Summary

Use when operating OpenRig with the rig CLI and you need the shipped command surface for identity, inventory, communication, lifecycle, specs, recovery, or agent-facing JSON output.

Files · 1

View on GitHub

SKILL.md

1	# OpenRig User
2
3	This is an as-built guide to the shipped `rig` CLI.
4	Use current code and `rig ... --help` as ground truth if anything here ever conflicts with older planning docs.
5
6	This is not the config-layer or builder guide. Use the substrate control-plane guidance for `rigx`
7	and experimental overlays. Use the OpenRig builder guidance when changing OpenRig behavior,
8	doctrine, or release posture.
9
10	## Coordination primitives — when to use which
11
12	Three coordination surfaces, used together for forward-momentum work. Internalize this
13	on first read — it shapes every turn you take in a rig.
14
15	### `rig send <seat> "<text>"` — intra-pod direct messaging / nudges
16
17	Use when you need to ask a quick question or give a teammate context that does not
18	carry handoff semantics. NOT for durable work. NOT for state that must survive
19	across turns. The message lands in the target's pane; there is no durable queue
20	record. The CLI prints `Sent to ...` (and `Verified: yes/no` with `--verify`); read
21	the receipt and move on.
22
23	Example:
24
25	```bash
26	rig send reviewer@acme-web "Heads up — filing the per-commit handoff on the search-filters slice at the current tip." --verify
27	```
28
29	### `rig queue create --source <X> --destination <Y> --tags <...> --body "<...>"` — durable work item
30
31	Use for any substantive work that must not fall through chat — slice handoffs,
32	guard verdicts, QA results, full-tip reviews, multi-item batches. Survives agent
33	restarts. Tracked in the daemon SQLite schema. Surfaces in Project / queue views
34	+ in the destination seat's inbox. Tag with mission / slice / gate / checkpoint
35	so future-you (and any peer) can find it.
36
37	Body discipline: substantive bodies go through a temp-file pattern, not inline
38	`--body` with raw backticks — `rig queue create` body parsing breaks on
39	unescaped backticks and rejects flag-like tokens.
40
41	Example:
42
43	```bash
44	rig queue create \
45	--source builder@acme-web \
46	--destination reviewer@acme-web \
47	--tags "mission:site-relaunch,slice:02-search-filters,gate:guard,handoff:per-commit,checkpoint:bug-1" \
48	--body "$(cat /tmp/per-commit-body.txt)"
49	```
50
51	### `rig queue handoff <qitem-id> --to <next> ...` — hot-potato handoff
52
53	Use when you have completed your turn on a qitem and the work moves to the next
54	owner. This is forward momentum. The ball passes to the destination seat;
55	chain-of-record (the prior qitem id) is preserved so the verdict trail is intact;
56	tags carry the phase boundary forward (e.g. `gate:guard` → `gate:qa`).
57
58	Example:
59
60	```bash
61	rig queue handoff qitem-20260601012431-d78aa805 \
62	--to qa@acme-web \
63	--tags "mission:site-relaunch,slice:02-search-filters,gate:qa,handoff:adversarial-dogfood"
64	```
65
66	### §1b doctrine — turn ends by passing the ball
67
68	**A turn ends by passing the ball, never by going idle holding the slice waiting
69	on a confirmation the process does not include.** If the work was authorized, the
70	per-commit guard + adversarial QA + orch heavy-verify are the guardrails — not an
71	operator pre-commit gate. Do the authorized work and pass the ball.
72
73	Valid pauses are only:
74
75	- A genuine blocker — file a blocked-state qitem against the blocking peer or
76	surface explicitly to orch.
77	- A scope-or-architecture question that requires owner input and changes the
78	plan — surface to orch with the specific decision needed.
79
80	Implementing already-authorized work is neither of these. Proceed without
81	phantom-gating on an imagined "next prompt" or "operator confirmation" that the
82	process does not require.
83
84	### Anti-patterns
85
86	- Using `rig send` for durable work → use `rig queue create` instead. Sends do
87	not survive restarts and do not show up in queue/project views.
88	- Idle-holding a slice for an imagined "next prompt" or "operator confirmation"
89	that the process does not require → pass the ball via `rig queue handoff` and
90	proceed to the next slice or stand by for the inbound verdict. See the §1b
91	doctrine above.
92	- Hand-coding `rigx queue` for new work → `rig queue` is the daemon-backed
93	canonical surface since the 2026-05-11 host-CLI fix. `rigx queue` is a
94	recovery-only fallback; qitems written via `rigx queue` are invisible to
95	daemon-backed reads and break fleet-wide routing discipline.
96	- Inlining a multi-line / backtick-heavy body into `rig queue create --body`
97	→ write the body to `/tmp/<descriptive-name>.txt` first, then
98	`--body "$(cat /tmp/<file>.txt)"`. The body parser does not tolerate raw
99	backticks or flag-like tokens inline.
100
101	## Runtime-Gated Coordination Primitives
102
103	OpenRig v0.3.1 is published publicly as `@openrig/cli@0.3.1` and GitHub Release
104	`v0.3.1`. It includes the bundled PL-004 Coordination Primitive System: Phase A
105	`rig stream` / `rig queue`, Phase B `rig project` / `rig view`, Phase C
106	`rig watchdog`, and Phase D `rig workflow` / `workflow-

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

openrig-user

56stars9forks

View on GitHub

How to install openrig-user?

mvschwarz/openrig/openrig-user

$npx -y skills add mvschwarz/openrig --skill openrig-user

Installs into the current project.

Summary

Use when operating OpenRig with the rig CLI and you need the shipped command surface for identity, inventory, communication, lifecycle, specs, recovery, or agent-facing JSON output.

Files · 1

View on GitHub

SKILL.md

1	# OpenRig User
2
3	This is an as-built guide to the shipped `rig` CLI.
4	Use current code and `rig ... --help` as ground truth if anything here ever conflicts with older planning docs.
5
6	This is not the config-layer or builder guide. Use the substrate control-plane guidance for `rigx`
7	and experimental overlays. Use the OpenRig builder guidance when changing OpenRig behavior,
8	doctrine, or release posture.
9
10	## Coordination primitives — when to use which
11
12	Three coordination surfaces, used together for forward-momentum work. Internalize this
13	on first read — it shapes every turn you take in a rig.
14
15	### `rig send <seat> "<text>"` — intra-pod direct messaging / nudges
16
17	Use when you need to ask a quick question or give a teammate context that does not
18	carry handoff semantics. NOT for durable work. NOT for state that must survive
19	across turns. The message lands in the target's pane; there is no durable queue
20	record. The CLI prints `Sent to ...` (and `Verified: yes/no` with `--verify`); read
21	the receipt and move on.
22
23	Example:
24
25	```bash
26	rig send reviewer@acme-web "Heads up — filing the per-commit handoff on the search-filters slice at the current tip." --verify
27	```
28
29	### `rig queue create --source <X> --destination <Y> --tags <...> --body "<...>"` — durable work item
30
31	Use for any substantive work that must not fall through chat — slice handoffs,
32	guard verdicts, QA results, full-tip reviews, multi-item batches. Survives agent
33	restarts. Tracked in the daemon SQLite schema. Surfaces in Project / queue views
34	+ in the destination seat's inbox. Tag with mission / slice / gate / checkpoint
35	so future-you (and any peer) can find it.
36
37	Body discipline: substantive bodies go through a temp-file pattern, not inline
38	`--body` with raw backticks — `rig queue create` body parsing breaks on
39	unescaped backticks and rejects flag-like tokens.
40
41	Example:
42
43	```bash
44	rig queue create \
45	--source builder@acme-web \
46	--destination reviewer@acme-web \
47	--tags "mission:site-relaunch,slice:02-search-filters,gate:guard,handoff:per-commit,checkpoint:bug-1" \
48	--body "$(cat /tmp/per-commit-body.txt)"
49	```
50
51	### `rig queue handoff <qitem-id> --to <next> ...` — hot-potato handoff
52
53	Use when you have completed your turn on a qitem and the work moves to the next
54	owner. This is forward momentum. The ball passes to the destination seat;
55	chain-of-record (the prior qitem id) is preserved so the verdict trail is intact;
56	tags carry the phase boundary forward (e.g. `gate:guard` → `gate:qa`).
57
58	Example:
59
60	```bash
61	rig queue handoff qitem-20260601012431-d78aa805 \
62	--to qa@acme-web \
63	--tags "mission:site-relaunch,slice:02-search-filters,gate:qa,handoff:adversarial-dogfood"
64	```
65
66	### §1b doctrine — turn ends by passing the ball
67
68	**A turn ends by passing the ball, never by going idle holding the slice waiting
69	on a confirmation the process does not include.** If the work was authorized, the
70	per-commit guard + adversarial QA + orch heavy-verify are the guardrails — not an
71	operator pre-commit gate. Do the authorized work and pass the ball.
72
73	Valid pauses are only:
74
75	- A genuine blocker — file a blocked-state qitem against the blocking peer or
76	surface explicitly to orch.
77	- A scope-or-architecture question that requires owner input and changes the
78	plan — surface to orch with the specific decision needed.
79
80	Implementing already-authorized work is neither of these. Proceed without
81	phantom-gating on an imagined "next prompt" or "operator confirmation" that the
82	process does not require.
83
84	### Anti-patterns
85
86	- Using `rig send` for durable work → use `rig queue create` instead. Sends do
87	not survive restarts and do not show up in queue/project views.
88	- Idle-holding a slice for an imagined "next prompt" or "operator confirmation"
89	that the process does not require → pass the ball via `rig queue handoff` and
90	proceed to the next slice or stand by for the inbound verdict. See the §1b
91	doctrine above.
92	- Hand-coding `rigx queue` for new work → `rig queue` is the daemon-backed
93	canonical surface since the 2026-05-11 host-CLI fix. `rigx queue` is a
94	recovery-only fallback; qitems written via `rigx queue` are invisible to
95	daemon-backed reads and break fleet-wide routing discipline.
96	- Inlining a multi-line / backtick-heavy body into `rig queue create --body`
97	→ write the body to `/tmp/<descriptive-name>.txt` first, then
98	`--body "$(cat /tmp/<file>.txt)"`. The body parser does not tolerate raw
99	backticks or flag-like tokens inline.
100
101	## Runtime-Gated Coordination Primitives
102
103	OpenRig v0.3.1 is published publicly as `@openrig/cli@0.3.1` and GitHub Release
104	`v0.3.1`. It includes the bundled PL-004 Coordination Primitive System: Phase A
105	`rig stream` / `rig queue`, Phase B `rig project` / `rig view`, Phase C
106	`rig watchdog`, and Phase D `rig workflow` / `workflow-

People who liked this also viewed

6 picks

Type