English | 简体中文
A repository-native engineering workflow for humans and AI agents.
RSP turns unclear intent into shaped, implemented, reviewed, and verified software changes while keeping project knowledge durable and work recoverable. It uses ordinary repository files—Rules, Specs, and Plans—rather than hidden workflow state.
- Shape ambiguous work into an executable Change.
- Resolve design questions from repository evidence before implementation.
- Route diagnosis, implementation, risk-selected test-first work, review, and release work to explicit capabilities.
- Preserve current facts, lasting rationale, scoped instructions, and completed history in the right owners.
- Keep authority visible: RSP never infers permission to commit, publish, deploy, or approve work.
RSP selects the next responsibility from the task and evidence, not a fixed stage pipeline. A settled authorized task can proceed directly to implementation and its own checks; design, review, coordination and lifecycle closeout apply only when needed and permitted.
RSP requires Node.js 22 (>=22). Run setup from the target project root. Later rsp examples assume that command is available; otherwise invoke the same selected package through npx -y @oevery/rsp@latest <command>. Use the current stable release:
npx -y @oevery/rsp@latest init --with-project-setup
# fill .rsp/changes/project-setup.md
# fill .rsp/specs/design.md
npx -y @oevery/rsp@latest doctor
npx -y @oevery/rsp@latest statusThen create and focus one tracked change:
rsp create improve-login "Make login failures actionable"
rsp focus improve-login
rsp show improve-loginFocus is a set: the setup Change may still be focused alongside improve-login. Use the explicit name to inspect it; show --focused requires exactly one marker.
Confirm that doctor reports the intended setup and status shows the expected work. These are deterministic observations, not semantic acceptance. Follow the nearest AGENTS.md, keep the selected Change current and establish applicable required verification, reusing traceable passing evidence when its tested boundary and relevant inputs still apply. Before authorized archive, decide necessary knowledge updates, converge the whole Change and check current readiness.
Read the full getting-started guide.
.rsp/
├── rsp-rules.md # minimal fallback protocol
├── specs/ # current contracts, boundaries, and constraints
├── changes/ # open work
├── focus.d/ # markers selecting work; optional short recovery capsules
└── archives/ # completed history
A Change is one Markdown file with canonical Proposal, Spec, Design, Tasks, Verify, and Blockers sections. Stable facts belong in Specs, lasting rationale in Decision Records, and scoped operating instructions in the nearest project-owned AGENTS.md.
- Getting started
- Core concepts and artifact ownership
- Daily workflow
- Skills and managed work
- Configuration reference
- CLI reference
- 3.0 migration guide and 3.1 migration guide
- Release notes
- Maintainer tests and Skill validation
- Repository context and contract navigation
- Authoritative architecture and Specs and maintainer research
Run the documentation locally:
pnpm docs:dev
pnpm docs:check
pnpm docs:buildThe site is only a presentation layer over the Markdown in this repository. It adds bilingual navigation, local search, and page outlines without introducing a content database or runtime service.
RSP is a tool-agnostic file convention and works with any assistant or editor that can read project files. Humans start here; agents follow the nearest AGENTS.md, load the project Core through host Skill discovery or .agents/skills/rsp/SKILL.md when available, and use .rsp/rsp-rules.md only when the Skill is unavailable. Root skills/ contains authored sources in the RSP repository, not the consumer installation entry.
The current source candidate installs the seven core Skills together with rsp skills install. Individual named installs are unsupported; each capability may still be invoked directly and reads shared Core definitions on demand. Structural discovery is now a conditional method of Review. See the Skill migration guide for protected upgrades from older installations.
RSP is licensed under the MIT License.