Explore skills
Showing 901–930 of 7156 skills
Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexYC-style product validation using six forcing questions. Pressure-tests a feature idea before it becomes a requirement — ensuring real demand, a clear wedge, and evidence behind assumptions.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexMulti-perspective review of a feature plan or requirements doc before development begins. Evaluates from strategy, design/UX, and engineering angles to catch gaps early.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when assigned a review or when an authored review boundary is reached.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexSystematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when implementing any feature or bugfix, before writing implementation code
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when about to claim work is complete, fixed, or passing, or before committing or creating PRs
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when the person runs an OpenRig team of agents on this machine and wants it to do some work, wants to know how that work is going, has a question from the team to answer, or wants to read what the team returned. Works through the `rig` command in your shell; no MCP server is needed.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when creating, refreshing, packaging, inspecting, promoting, or deprecating a named per-seat starting point — Agent Starter manifest authoring, the 6-state lifecycle (captured → named → inspectable → used → promoted → deprecated), provenance honesty, and refusal rules. NOT a VM image; a managed starting point composed from agent role + startup context + optional native session source + provenance.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when project policy calls for a human decision or update, a human delivery is pending or failed, or a reply must resume the right work.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when designing multi-agent topologies that run ON OpenRig — authoring RigSpec and AgentSpec files for new rigs, creating agent startup content (guidance / skills / culture), or diagnosing why a launched rig's agents aren't behaving as intended. NOT for changing OpenRig itself (use developing-openrig); NOT for ordinary CLI operation of an existing rig (use openrig-user). Covers the full authoring lifecycle from user intent to validated, launchable rig.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when opening OpenRig fleet terminals into cmux — turning a rig, pod, mission, slice, or saved view into live agent tiles via `rig terminal --provider cmux`, or driving cmux on an agent's request. Same OpenRig view semantics as openrig-herdr (the verbs, honest-partial/degrade, read-only cross-rig, scroll/copy, same-size-only duplicates); cmux is the **best-effort** provider (herdr is the default and the proof-gated one). Prefer openrig-herdr unless cmux is specifically wanted.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when opening OpenRig fleet terminals as a herdr wall — turning a rig, pod, mission, slice, or saved view into live interactive agent tiles via `rig terminal`, watching another rig read-only, or driving herdr on an agent's request ("open all my rigs + a mission as views"). Covers the `rig terminal open|views|status` verbs, the honest-partial/degrade reading of the result, the read-only-by-construction rail for cross-rig views, scroll/copy out of the box, and the same-size-only duplicate-pane limit. herdr is the default, proof-gated provider.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when an agent running inside OpenRig needs the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade, systematic debugging, queue triage, or implementation planning; also when the agent doesn't know what applies or nothing is projected on cold boot. Installing, starting or updating OpenRig, getting back to a team or bringing a stopped one back from a person's own session is the rigs skill.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse 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.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when an agent is preparing or performing an OpenRig CLI/daemon upgrade and must preserve live seats, verify each mutation, or reconcile managed plugin and skill files without overwriting local work.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension boundary, or auditing a bundle for portability. Covers the 4 failure modes that prevent bundles from working anywhere but the operator's machine, and the inspect-before-install discipline.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when authoring a rig spec member or `rig expand` payload that needs to start a new managed seat from a prior runtime conversation source — `session_source: { mode: fork, ref: { kind, value } }`. v1 supports `mode: fork` with `ref.kind: native_id` for Claude and Codex. The new seat persists a NEW post-fork token; the parent token is NEVER written onto the new seat. NOT for restoring an existing seat or for artifact-backed mental-model rebuild.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexQuickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexGather and distill context from meetings, competitors, regulatory sources, and internal discussions. Produces background.md for a feature and updates shared context docs when new knowledge is discovered.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexGenerate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexYC-style product validation using six forcing questions. Pressure-tests a feature idea before it becomes a requirement — ensuring real demand, a clear wedge, and evidence behind assumptions.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexMulti-perspective review of a feature plan or requirements doc before development begins. Evaluates from strategy, design/UX, and engineering angles to catch gaps early.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when assigned a review or when an authored review boundary is reached.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexSystematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
mvschwarz/openrig
Stars: 8.8kClaude CodeCodex