Set up scoped builder and read-only validator agent packets with only the required teams for an end-user request.
RStack’s sandbox model is simple: the orchestrator plans the work, then each builder/validator receives a bounded task packet instead of the whole project and whole catalog.This matches current agent-platform trends: multi-agent orchestration, explicit handoffs, tool governance, typed output contracts, traceability, and cost-aware context selection.
user request → orchestrator clarifies and plans → profile selects enabled domains and plugins → task packet is created → builder works with write-capable tools → validator reviews with read-only tools → contracts and evidence land in .rstack/runs/<run-id>/tasks/<task-id>/
npm install rstack-agentsnpx rstack-agents init --profile lean-mvp # small teamnpx rstack-agents init --profile business-flex # balanced business teamnpx rstack-agents init --profile enterprise-webapp # broad enterprise team
For a specific user ask, edit .rstack/rstack.config.json to keep only the relevant domains.Example: “Help me upgrade this Node API with tests and security review”:
5. How to install only the required agent packs today
Today, the npm package ships the complete catalog. For a scoped project, use a profile plus project-local plugin copies:
# List available packsnpx rstack-agents list pluginsnpx rstack-agents list agents# Copy only relevant domain packs into this projectnpx rstack-agents add plugin backend-developmentnpx rstack-agents add plugin unit-testingnpx rstack-agents add plugin security-scanning# Validate before runningnpx rstack-agents validate
Do not copy random GitHub agent files directly into production RStack runs. Read open-source patterns, adapt the ideas, keep licenses intact, and validate the local agent frontmatter/contracts before enabling them.
Use this pattern when the end user says “help me upgrade this application”:
Use RStack business-flex profile.Goal: upgrade this application safely.First inspect package files, test setup, framework, CI, security posture, and docs.Plan only the minimum required builder/validator teams.Prefer existing project conventions.Create budget envelope and routing explanation before build.Builder must run relevant tests and write builder.json.Validator must be read-only and write validation.json.Do not claim DONE without command evidence.