using-arise

Original：🇺🇸 English
Translated

Use when working with the `arise` CLI to check readiness, generate review-first plans from strict PRDs or GitHub issues, inspect `.arise/` artifacts, execute reviewed plans, or recover interrupted and integration-blocked runs.

11installs
Sourcemichaelasper/arise
Added on

NPX Install

npx skill4agent add michaelasper/arise using-arise

Tags

Translated version includes tags in frontmatter
arise-clicoding-agentcli-toolworkflow-orchestrationdevelopment-utility

SKILL.md Content

View Translation Comparison →

Using Arise

Overview

Arise is a local-first orchestration CLI for coding-agent work. Prefer review-first commands before any execution, and treat persisted 
.arise/
state as the record of what happened.

When to Use

  • Asked to use 
    arise
    , 
    .arise/
    , 
    roadmap
    , 
    live
    , 
    history
    , 
    resume
    , 
    replay
    , or 
    recover
    .
  • Need to turn a strict PRD or GitHub issue body into a reviewable YAML plan.
  • Need to inspect saved plans, run state, worktrees, or recovery bundles.
  • Do not use for ordinary repo edits that do not involve Arise workflows.

Quick Reference

GoalCommandNotes
Use an installed binary
arise ...
Normal end-user path.
Use a source checkout
cargo run -p arise-cli -- ...
Use when contributing from the Arise repo. The package name is 
arise-cli
; 
cargo run -p arise --
fails in this workspace.
Check readiness
... doctor
Read the selected provider profile and next action before planning.
Initialize config
... init
Safe to rerun.
Plan safely from a PRD
... start --prd <file> --dry-run --no-auto-run
Dry-run still writes 
.arise/plans/
artifacts.
Plan from a GitHub issue
... start --github-issue owner/repo#123 --dry-run --no-auto-run
Use only when the issue body already follows the strict PRD shape.
Review the generated planopen 
.arise/plans/<slug>/generated-plan.arise.yaml
Also inspect 
revisions/rev-<n>/
before execution.
Execute a reviewed plan
... run .arise/plans/<slug>/generated-plan.arise.yaml
Non-dry-run execution needs a Git repo with at least one commit so worktrees can be created.
Inspect run state
... live
, 
... history --limit 10
Start here before rerunning anything.
Recover safely
... recover inspect <run-id>
Use 
resume
for interrupted runs; use 
replay
after fixing an 
integration-blocked
phase; use 
recover repair
only when inspection recommends it.
Work from a roadmap
... roadmap inspect
, 
... roadmap plan
, 
... roadmap sessions
, 
... roadmap resume
Use when the repo already treats 
docs/roadmap.md
as a first-class Arise input.

Minimal Flow

bash
arise doctor
arise start --prd path/to/prd.md --dry-run --no-auto-run
find .arise/plans -maxdepth 2 -name generated-plan.arise.yaml
If the plan is sound, review the saved YAML and only then run 
arise run ...
.

Common Mistakes

  • Treating 
    --dry-run
    as side-effect free. Planning still writes 
    .arise/
    artifacts.
  • Skipping plan review and going straight to execution.
  • Using 
    resume
    for a blocked phase checkpoint instead of inspecting first and then using 
    replay
    .
  • Running mutating execution in a repo with no commit, which breaks worktree creation.
  • Ignoring provider readiness. Even dry-run planning still depends on a working planner provider.
  • Sharing 
    .arise/
    bundles without review; they can contain prompts, logs, file paths, and issue content.