cd your-projectnpm install rstack-agentsnpx rstack-agents init --profile business-flex # auto-detects pi | claude-code | operator | custom
init sets up .rstack/, writes the active business profile and budget policy,
registers the project with the Business Hub, scaffolds bootstrap files
(SOUL.md, HEARTBEAT.md, and framework-specific CLAUDE.md or AGENTS.md),
writes the framework-specific glue,
and prints next steps — idempotent and non-destructive. New to your AI framework
itself? See
Install your framework for the
per-tool setup, then run the command above.
The sections below are the manual / asset-based paths. You only need them
for frameworks without a native adapter (Codex, Gemini, universal) or if you
prefer wiring assets yourself.
Profiles write .rstack/rstack.config.json and .rstack/budget.json. They guide enabled domains, plugin priority, dashboard pages, routing explanations, and budget envelopes. See Business Flex Profiles.
The native Pi adapter gives RStack lifecycle hooks, tool gating, session events, and the full governed harness.
# Install from npmpi install npm:rstack-agents# Install from local checkoutpi install /path/to/SDLC-rstack# One-off run without installingpi -e /path/to/SDLC-rstack/extensions/rstack-sdlc.ts
Recommended:npx rstack-agents init --framework claude-code scaffolds CLAUDE.md, SOUL.md, and HEARTBEAT.md automatically.Manual asset copy (optional). Note: no rstack-agents command creates or
refreshes these copies — init does not write .claude/agents/rstack/ or
.claude/commands/rstack/. If you make them, they are unmanaged: re-copy
after upgrading the package. The supported Claude Code surface without them
is the bridge tools + the rstack-agents CLI + the settings hooks.
Use RStack SDLC from $RSTACK_HOME.Read agents/core/orchestrator.md first.Use agents/core/builder.md for implementation tasks.Use agents/core/validator.md for read-only verification.Use agents/sdlc/ for lifecycle routing.Use skills/ and plugins/ only when relevant.Write run state under .rstack/runs/<run_id>/.Require specs, approvals, traceability, builder.json, validation.json, and command evidence.Never claim DONE without evidence.
