Skip to main content

Overview

Claude Code can use project/user subagents and slash commands. RStack runs in Claude Code today as portable agent assets — the Pi-native lifecycle hooks are not available, but the full agent/skill/plugin library is.
init creates .rstack/, scaffolds CLAUDE.md, SOUL.md, and HEARTBEAT.md from the package templates, writes .claude/rstack-sdlc.md, and optionally a SessionStart hub hook snippet. Existing files are never overwritten.

How invocation works

Claude Code does not call sdlc_start or any other Pi tool directly. It invokes RStack through portable files: The practical difference from Pi is enforcement. Claude Code can follow RStack’s orchestrator/builder/validator contracts and write .rstack/runs/<run_id>/ state, but the package cannot intercept every Claude Code tool call the way the Pi tool_call hook can. Use approval and validation contracts in Claude Code, but treat destructive-action blocking as a Pi-native guarantee unless a future Claude Code adapter adds equivalent tool gating.

Manual asset copy (optional)

If you prefer a local vendor copy instead of reading from node_modules/rstack-agents/. Note: these copies are manual and unmanaged — rstack-agents init does not create or refresh any of them; re-run the copy after upgrading the package.

CLAUDE.md configuration

Run init, or copy the canonical template from the package:
The template covers orchestrator/builder/validator routing, .rstack/rstack.config.json profile awareness, run state under .rstack/runs/<run_id>/, and optional SessionStart hub hooks.

Limitations vs. Pi

A Claude Code adapter with native tool gating is on the roadmap.