Plan agent replacements while keeping the same workspace identity. The skill separates creating a successor from assigning it to the existing role, records both outcomes, and prepares durable handover notes and traceable replacement history.
- Replace an agent while preserving its workspace identity
- Prepare recap notes for a successor
- Track successor creation and assignment separately
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Check the health of the HashiCorp Vault instance in an OpenRig environment and manage stored secrets. Use its API to write, read, list, or delete entries and explain how secret paths are organized.
- Checking whether the local Vault instance is healthy
- Storing or retrieving secret values
- Listing secret paths and explaining their contents
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Plan an agent's handover to a fresh successor before its context fills up. Prepare transfer materials, preserve the role's address, record tenure history, and explicitly transfer recurring duties and authority while keeping a way to consult retained predecessors.
- Planning a handover before an agent's context fills up
- Transferring recurring duties and authority
- Recording an agent role's tenure history
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Helps older OpenRig instructions that reference software-for-agents lead to its maintained successor, agent-operated-software. This temporary compatibility redirect identifies where to find the current architecture and operating guidance.
- Following older OpenRig instructions
- Finding guidance under the successor skill name
- Checking the compatibility redirect's retirement schedule
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Plan how agents retain active work across conversation compaction, context loss, and restarts. Organize restoration packets that preserve purpose, progress, ownership, and constraints, distinguish resume from fork or rebuild, and check whether work actually resumes correctly.
- Prepare restoration materials before conversation compaction
- Preserve task purpose and ownership across a restart
- Distinguish native resume, fork, and artifact-based rebuild
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Open terminal views for OpenRig agents in cmux, grouped by rig, pod, mission, slice, or saved view. Inspect connection health and view agent sessions with read-only access where required, while keeping the underlying sessions running.
- View a rig's agent terminals together in cmux
- Monitor mission or slice terminals in read-only mode
- Reopen a saved terminal view
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Design an OpenRig agent team around a project goal. Create team and agent specifications, role guidance, and collaboration rules, then validate the setup and diagnose problems with startup instructions or agent coordination.
- Designing an implementation and QA pair
- Creating a team with development and independent review
- Writing role guidance and team collaboration rules
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Look up exact syntax, options, JSON output, defaults, and error meanings for a known OpenRig command. Use the reference to check command behavior and diagnose runtime differences against the installed help and running daemon.
- Checking required flags for a known rig command
- Looking up queue commands and handoff syntax
- Investigating command errors and daemon compatibility
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Guide OpenRig CLI and background service upgrades while protecting active sessions and local file changes. The skill provides staged checks, verified database backups, selective plugin refreshes, and migration helpers, with evidence checked after each change.
- Upgrading OpenRig while preserving active sessions
- Backing up and checking the database before an upgrade
- Refreshing managed plugins while preserving local edits
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Set up an OpenRig team for ongoing repository work, with clear ownership, implementation, independent review, and handoffs. Choose direct coordination, a task queue, or an explicit workflow, then expand the team as authorized work requires.
- Starting a builder and reviewer team for a repository
- Keeping ownership visible across task handoffs
- Choosing direct work, a queue, or a workflow
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Plan and verify OpenRig startup, shutdown, and recovery. Compare reported status with actual running sessions, distinguish recovery outcomes, and define reboot tests that expose partial failures instead of hiding them behind a fresh launch.
- Checking rig status after a host reboot
- Designing recovery tests across runtimes
- Investigating partially restored agent sessions
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Configure a new OpenRig agent seat, a managed place for an agent to run, using a prior Claude or Codex conversation. Covers fork settings, new session identities, and checks that distinguish forking from restoring.
- Create a new agent seat from an earlier conversation
- Add conversation source settings to a rig expand payload
- Distinguish conversation forks from seat restoration
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Define reusable OpenRig agent setups, roles, and workflows in specification files. Review dependencies that prevent use on another host, distinguish specifications from bundles and extensions, and verify both file structure and actual execution.
- Defining reusable agent roles and workflows
- Reviewing specifications for use on another host
- Testing specifications in a clean OpenRig environment
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Change a running OpenRig setup by adding or removing agent seats, connecting existing sessions, or attaching terminals. Guides checks for roles, startup context, permissions, and session identity so the setup reflects each change correctly.
- Add agent seats to a running rig
- Remove seats and clean up remaining references
- Connect an existing session to an OpenRig node
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Guides the design and review of agent startup context, including role files and links to authoritative records. It helps identify stale guidance, missing updates, overloaded startup files, and instructions that lose the purpose of the work.
- Designing startup files for a new agent
- Reviewing stale guidance used by running agents
- Separating role information from reusable procedures
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Turn a development-ready feature's specifications, customer context, demand evidence, and mockups into a concise executive summary. Give sales, leadership, and engineering one shared document covering the problem, solution, key decisions, scope, dependencies, metrics, and audience-specific questions.
- Create a shared feature briefing for sales, leadership, and engineering
- Summarize customer needs and reasons to prioritize a feature
- Clarify key decisions, exclusions, and dependencies
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Collects and summarizes background research for a product feature, including customer needs, competitors, regulations, and internal decisions. Produces a source-linked background.md and updates shared context documents when findings are useful across features.
- Gathering background research for a new feature
- Organizing customer requests and pain points
- Reviewing competitor approaches and relevant regulations
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Find and load the appropriate skill for an agent working inside OpenRig. This index maps situations such as recovery, handover, debugging, and planning to relevant guidance, with commands that retrieve content matching the installed CLI.
- Find relevant guidance when an agent first starts
- Locate skills for recovery or seat handover
- Find procedures for debugging or implementation planning
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Review feature plans before development from business strategy, user experience, and engineering perspectives. Receive scored assessments, specific gaps tied to requirements, and prioritized actions that clarify what must change before the team starts building.
- Checking a feature specification before development
- Reviewing screen states and accessibility requirements
- Assessing scope against business priorities
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Turn rough feature ideas into a clear SPEC.md through focused questions. Define target users, business rules, current scope, and acceptance criteria based on observable results, giving developers or AI agents concrete requirements to implement.
- Turning rough feature ideas into requirements
- Defining observable acceptance criteria
- Clarifying current scope and exclusions
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Create screen mockups at three levels: text wireframes, standalone HTML files, or working prototype pages. Use requirements, existing app styles, and real project data to show layouts and interactions for review or testing.
- Sketch screen layouts while writing requirements
- Deliver HTML mockups alongside requirements
- Test interactions with existing components
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Guide a development team from an assigned user outcome through implementation, testing, and handoff. It covers reproducing defects, checking behavior against requirements, involving design when needed, and reporting the exact changes, verification results, and remaining uncertainty.
- Start implementation from the assigned user outcome
- Reproduce a defect and verify its repair
- Review delivered behavior against requirements
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Coordinate work across an OpenRig agent team with clear assignments, attached context, completion criteria, and selected review checkpoints. Track queue status, identify blocked or idle owners, and resolve handoff gaps while leaving implementation with the assigned agents.
- Assign agent tasks with context and completion criteria
- Identify blockers and missed handoffs from queue status
- Route reviews at the agreed milestones
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026
Turn rough meeting notes, customer requests, and product ideas into structured backlog entries, a list of possible improvements. Capture who needs each idea and why, categorize it, and update matching entries with new evidence.
- Capturing feature ideas after a meeting
- Recording requests from customers or sales
- Logging product gaps found in competitor research
mvschwarz/openrig☆ 7.8KUpdated Oct 19, 2026