
Openrig Software Factory
Use when a user wants a continuing software team for a real repository, or has a first...
Install
npx skills add mvschwarz/openrig --skill openrig-software-factory -g -a claude-code -y- Repository
- mvschwarz/openrig8.5k
- Category
- Engineering
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 2,509 tokens
- Runs scripts
- No, instructions only
What it does
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.
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. 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.
