orbit

A Claude Code plugin that runs every task through the same steps: pick the flow, build the smallest change, review it, ship it. Same steps in every repo, so you don't repeat yourself each session.

Orbit is mostly pstack by Lauren Tan, trimmed and ported to Claude Code. See Credits.

Install

/plugin marketplace add aayushbtw/orbit
/plugin install orbit@orbit

Auto-update is off for third-party marketplaces. Turn it on or run claude plugin update orbit@orbit.

A task, start to finish

flowchart TD
    start["/orbit:start <goal>"] --> flow{Pick the flow}
    flow -- investigate --> answer[Answer, no commit]
    answer --> next
    flow -- bug, feature, refactor,<br/>perf, hillclimb --> wt[Own worktree]
    flow -- large or cross-cutting --> fio["/orbit:figure-it-out<br/>designs the steps"]
    fio --> wt
    wt --> big{Adds module or<br/>over 3 files?}
    big -- yes --> advisor[Advisor reviews plan]
    big -- no --> build
    advisor --> build
    subgraph loop [Build loop]
        build[poteto-agent writes unit] --> review[Claude reviews, verifies]
        review --> commit[gitops commits]
        commit -- next unit --> build
    end
    commit -- all units done --> ship
    subgraph ship ["/orbit:ship"]
        check[Run checks] --> clean[deslop, no-comments]
        clean --> panel[Reviewers Opus + Sonnet]
        panel --> verify[Verifier]
        verify --> docs[Docs]
        docs --> land[Main, or PR after CI]
    end
    land --> next([Next: line])

Loading

Full walkthrough

What do I run?

flowchart LR
    q{What now?}
    q -- new task or question --> start["/orbit:start <goal>"]
    q -- change built, land it --> ship["/orbit:ship"]
    q -- stop or switch model --> pause["/orbit:pause-safely"]
    pause -- new session --> pickup["/orbit:session-pickup"]
    q -- how or why code works --> how["/orbit:how or /orbit:why"]
    q -- Claude repeats a mistake --> correct["/orbit:correct"]

Loading

Every command: docs/usage.md

The Next: line

Every task ends with one Next: line. Do what it says.

Line	Means	You do
Next: nothing pending.	Task is done	/orbit:start your next goal
Next: /orbit:start <follow-up>	Outside the goal or needs your decision. Claude says which.	Run it when ready
Next: new session, then /orbit:session-pickup	Work was paused	Open a new session, run it

Correct usage

• Give /orbit:start the goal, not the steps. Orbit picks the flow and the steps.
• Don't land a change by hand. /orbit:ship runs the checks, the cleanup, the reviewer and the verifier, and a change never lands without them.
• Project differences (check command, PR landing, extra review sources) go in the project's ## Workflow block, not in chat.

Make it fit a project

Defaults assume Vite+, a worktree per change, and fast-forward onto main. If a project differs, list only what's different in its AGENTS.md:

## Workflow

- Check: `vpr check`, plus `vpr e2e` when the UI changed.
- Land: `pr`
- Review also checks: `docs/architecture.md`.

More in docs/usage.md:

• Project defaults and folder rules
• Background agents
• Principles and stack rules

Credits

Most of orbit is MIT work from pstack by Lauren Tan, cursor-team-kit, vercel-labs/agent-skills and emilkowalski/skills by Emil Kowalski. What came from where.

Orbit's own parts are the /orbit:start to /orbit:ship wiring and the project defaults. Differences from pstack lists where orbit departs and why.

Maintain

• Develop without installing: claude --plugin-dir ~/Projects/orbit. Check with claude plugin validate ..
• Vendored files are tracked in skills.json. Update them with /update-skills [name] from this repo.
• The reviewer may ask once to read the plugin folder for the review rubric and React rules. Allow Read(~/.claude/plugins/**) to skip the prompt.
• Release: bump version in .claude-plugin/plugin.json.