Skip to main content

Skills

Skills are reusable workflow instructions. They are Markdown files that describe how to approach a specific task — like code review, OWASP security checks, or API documentation. Location: skills/**/SKILL.md Example skill structure:
Skills are included in task packets when the orchestrator determines they are relevant. A builder working on an auth module might automatically receive the security-owasp and code-patterns skills.

Using skills from the CLI


Plugins

Plugins are domain packs. Each plugin bundles together:

Available plugin domains (sample)

How plugins are selected

The orchestrator selects plugins based on the task domain. For a task tagged backend:
  1. Looks up routing.json for the backend domain
  2. Selects plugin.backend-development
  3. Includes the plugin manifest and the specific nested agent/skill needed
  4. Adds it to the builder’s task packet

Adding plugins

Profile-scoped plugins

Business Flex profiles narrow which domains and plugin packs are considered during planning. For example, an API upgrade can keep only product/backend/QA/security/docs enabled instead of routing through the whole catalog:
See Business Flex Profiles and Builder & Validator Sandbox.

Writing a custom plugin

Create the plugin structure in .rstack/plugins/:
plugin.json:
The registry will pick up your plugin on the next rstack-agents validate run.

Prompts

Prompts are command-style workflow templates. They give the agent a scripted approach to common tasks. Location: prompts/*.md Count: 36 prompts included
Prompts are exposed as slash commands in Pi: