run-workflow

Validate and establish the proven rn-dev-agent operating sequence before a real device journey. The command loads the rn-workflow skill and executes its contract steps in order:

1. Read the project’s injected instructions and troubleshooting memory.
2. Detect the declared package manager (the packageManager field wins, lockfile inference is the fallback) and install dependencies with exactly that manager via the deterministic workflow-check preflight.
3. Inventory sessions, Metro, and devices read-only; scan learned actions — discovery never grants replay authority.
4. Classify a blocked session using only rn_session(action="status")’s recoveryRequirement and follow its typed next action, re-reading status after every recovery step, with a bounded stop when the same blocked projection recurs.
5. Bind one exact device (never the first ambient candidate, never force-stealing a claim), apply the reversible package integration, and build through the literal integrated package script.
6. Run only the requested proof, re-reading success from authoritative tool state; replay learned actions only via cdp_run_action.
7. Clean up in reverse order (device_snapshot action=close → stop_metro → restore_integration → release) and verify residue with the workflow-check postflight.

The outcome is a per-step readback table, or one actionable stop naming the exact remedy.

Usage

/rn-dev-agent:run-workflow [journey-description]

Steps 1–5 above (validation and authority establishment, through device binding and the managed build) run without a journey description; only the proof step requires one.