Getting Started¶
Use this path to go from a fresh install to a project-aware workflow you can monitor in Arcade.
rp1 adds repeatable development workflows to AI coding assistants. You install the CLI, initialize a repository, generate project context once, then run workflow skills for feature work, bug investigation, PR review, documentation, and team handoffs.
Start Here¶
| Step | Goal | Where to go |
|---|---|---|
| 1 | Install rp1 and connect at least one supported host tool. | Installation |
| 2 | Initialize a repository with rp1 init. |
Installation: Initialize your project |
| 3 | Generate project context so workflows understand your codebase. | Your first workflow |
| 4 | Choose a first tracked workflow that creates visible work. | Your first workflow |
| 5 | Open Arcade and inspect the run, artifacts, and any attention needed. | Your first workflow |
Invocation Patterns¶
The workflow is the same on each host. Only the invocation syntax changes:
| Host | Example |
|---|---|
| Claude Code | /build my-feature |
| OpenCode | /rp1-dev-build my-feature |
| Codex | $rp1-dev-build my-feature |
| GitHub Copilot CLI | /rp1-dev-build my-feature |
Pick Your First Outcome¶
-
Ship code
Turn a feature idea into requirements, a plan, implementation, and verification.
-
Review a PR
Run a structured review, inspect findings, and decide whether to block or proceed.
-
Monitor in Arcade
Watch active runs, open artifacts, follow external links, and respond to gates or feedback.
-
Bring in a teammate
Help another developer install rp1, build context, and choose a useful first workflow.
Prerequisites¶
Before you begin, you need:
- A supported AI coding assistant: Claude Code, OpenCode, Codex, or GitHub Copilot CLI
- A repository where you want rp1 to help with real work
After The First Run¶
Most users continue with:
- Feature development for larger changes that need requirements, planning, implementation, and release checks.
- Build Fast for smaller bounded tasks.
- PR review when the next decision is whether a branch is ready.
- Arcade whenever you want to monitor runs and give feedback on artifacts.
The .rp1 directory guide is available when you need to understand project files, sharing choices, or troubleshooting details. You do not need it to complete normal onboarding.