openrig-software-factory · git:20260925.4940c10 · 2026-09-25 · sha256 acf521214679770d
openrig-software-factory git:20260925.4940c10A
Immutable. This exact content never changes and is served at /api/v1/blob/acf521214679770d.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_adwezawngi4riv3c/acf521214679770d614679f6f903015465e0ab13d488ec777765dc3effb2da96.json
Then /plugin install openrig-software-factory@markdownregistry-adwezawngi4riv3c in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: openrig-software-factory
description: >-
Use when a user wants a continuing software team for a real repository, or has a
first OpenRig team and needs a repeatable path for reviewed work and later tasks.
metadata:
cli_surfaces_referenced:
- context get
- context list
- context show
- expand
- queue create
- queue handoff
- workflow compile
- workflow instantiate-lifecycle
openrig:
stage: WIP
transfer_test: pending
---
# OpenRig Software Factory
Start with a useful repository outcome and add coordination when it earns its
cost. A beginner can complete reviewed work without Workflow. These are choices
using existing capabilities, not stages everyone must graduate through.
## Choose how the team works
| Need | Start here | Add more when… |
| --- | --- | --- |
| One change, close human guidance | Manual/team work: give an owner the outcome, use repository instructions, implement and obtain the chosen independent check. | Work must survive turns or move between seats. |
| Continuing work with visible ownership | Queue-supported orchestration: use `rig queue create`, claim work, then `rig queue handoff` with the candidate/evidence to the next owner. Record real blockers and the continuation. No Workflow instance is needed. | Repeated steps need an explicit dependency graph and permitted exits. |
| An explicit execution contract | Workflow: inspect `rig workflow compile`, then deliberately use `rig workflow instantiate-lifecycle`. Advance its packets through the workflow projection mechanism. | The actual project needs reusable profiles, additional roles or gates. |
For the concrete queue loop, wake behavior and optional two-slice Workflow,
read [references/worked-example.md](references/worked-example.md). Installed copy:
`rig context get skills/core/openrig-software-factory/references/worked-example.md`.
A roadmap, YAML file or wake does not execute work or authorize a new outcome.
## Establish the working agreement
Read the repository instructions, current work and desired user-visible result.
Verify the intended instance, code/work roots, real seat addresses and native
readiness. Reuse a suitable small team; an existing agent can bootstrap it.
A kernel operator is optional and is not automatically the project owner.
Agree the work boundary, time/spend limit, who answers unresolved choices, and
when to stop: checked result, no authorized next work, exhausted budget, or a real
user/permission/provider blocker. Background daemon checks are not themselves
model turns, but delivered wakes and resumed work **can spend tokens**. Prefer
an event-driven wait to frequent empty reminders. Wakes cannot answer a user
question, clear a permission prompt or guarantee progress.
**Choose permissions before launching or assigning work.** Keep ordinary native
prompts, or deliberately select the user's permissive policy after explaining
its filesystem/network risks. Read the [permission guidance](../../../../../../../../docs/reference/getting-started.md#opt-in-permissive-operation)
(the installed `getting-started.md` has the same section). Check the effective
native mode: an OpenRig resource profile is not a permission profile, and a
Codex YOLO sandbox setting alone does not select its approval policy. Preserve
user defaults; never silently add global trust, network grants or bypass flags.
Keep purpose, acceptance, decisions and evidence in existing project files.
Deliver selected context and obtain each seat's scope reaction; retrieval alone
is not peer delivery. The owner carries the candidate through the chosen check
and bounded repairs, reports how to try it, and retains the next authorized task
or explicitly reports none. Preserve work and custody before a supported stop.
## Grow your factory
Choose the team size separately from the coordination method above:
1. **Use the two-agent starter.** Keep the existing owner and independent checker
while that pair meets the workload. The owner can implement and coordinate.
2. **Add one or two seats to the running rig.** This is the usual next step.
Follow [Grow the running team](references/worked-example.md#grow-the-running-team)
for a complete pod fragment, `rig expand` commands, readiness/context/work
assignment, and saving the expanded topology. Existing sessions need no
rebuild or down/up cycle solely to add capacity.
3. **Author a custom rig when you want a different structure.** Read
[OpenRig Architect](../openrig-architect/SKILL.md), available through
`rig context get skills/core/openrig-architect/SKILL.md`. Request:
“Design a user-owned rig for [outcome] using the compatible RigSpec/AgentSpec
guidance. Reuse suitable agents, define responsibilities and context, and
validate the files. Preserve the existing rig and agree any new launch.”
As independent work grows, the original owner can concentrate on orchestration,
multiple builders can implement separate outcomes, and the checker can retain
independent review capacity. Record that division explicitly; adding seats does
not assign work, change permissions or create parallelism. Agree file/worktree
boundaries and integration ownership, follow the project's existing review policy,
and keep active concurrency within the user's time/spend budget. Two seats are
an entry point, not a finished factory or a maximum.
## Read compatible guidance
Before installation, use this file and companion at the same published tag or
commit as the selected package. After installation:
```sh
rig --version
rig context list --json
rig context show skills/core/openrig-software-factory --json
rig context get skills/core/openrig-software-factory/SKILL.md
```
Compare build identity as well as version. Preserve missing, unreadable or older
recipe results; do not silently substitute newer main or skip a missing companion.
## Request to give your agent
> Help me achieve [observable change] in this repository. Read the compatible
> Software Factory recipe, choose the lightest useful team/queue/Workflow path,
> and keep the next owner visible. Preserve existing files and permissions.
> Agree time/spend limits, perform the authorized work and chosen independent
> check, and ask only about unresolved decisions or effects outside that scope.
> Keep publication and destructive changes out of this task.
## What has been observed
A bounded macOS/Codex trial on a private 0.5.14-based candidate completed
independently reviewed two-slice work, next-task pickup and a supported stop
with setup assistance. It required
**48 one-time approvals (34 owner, 14 checker)**. This is not an unattended or
low-friction result. A genuine product-decision wait/answer and automatic refocus
were not demonstrated; these revised instructions have not had a new native trial.
No fresh-account, other-platform/provider, restore or weeks-long autonomy claim.
When commands, defaults or permission semantics change, check this source and
companion together and regenerate their existing projections. Website guidance
should link to the same versioned recipe, not maintain another procedure.