| name | prd-reference |
| description | prd2 CLI reference for managing Rossum configurations across environments. Covers pull, push, deploy, purge commands, credentials, deploy files, attribute overrides, and project structure. Use when working with prd2, deployment workflows, or Rossum environment management. |
| user-invocable | false |
prd2 (Project Rossum Deploy) Reference
This skill provides a comprehensive reference for the prd2 deployment CLI used to manage Rossum.ai configurations across environments. For complete details, see reference.md.
IMPORTANT: Always use prd2 (v2). The original prd (v1) from the deployment-manager package is deprecated and should not be used. prd2 uses a different project structure, configuration format, and deployment model.
Safety Rules
Do not run prd2 push, prd2 deploy, or any Rossum write API call without explicit user approval. These commands modify remote environments. Always describe what you intend to push/deploy and wait for confirmation. prd2 pull (read-only) is fine without confirmation.
Edit local .py files, not JSON. When modifying hook code or formula logic, only edit the .py file. Never edit the code field in hook JSON or the formula property in schema.json — prd2 push syncs .py files into JSON automatically.
Getting a token quickly
If prd2 complains about credentials, don't go hunting through ~/.prd2/credentials.yaml, ~/.config/prd2/, or find ~ — that path has burned multiple sessions. Instead, ask the user for a curl-style token string from the Rossum UI ("Settings → API access") and call the MCP tool rossum_set_token with it. That sets the in-process credentials and prd2 picks them up via the standard ROSSUM_* env vars without filesystem changes.
Only fall back to inspecting credentials files if rossum_set_token is unavailable or the user explicitly wants the token persisted.
Non-interactive push
prd2 push is interactive by default (asks for diff confirmation), which deadlocks in non-TTY contexts. Use:
prd2 push --indexed-only -f
--indexed-only limits the push to objects actually staged for change (much faster, much safer than a full push).-f skips the confirmation prompt — only use this when you've already shown the diff to the user and they approved.
Use this knowledge when:
- Working with
prd2 CLI commands (pull, push, deploy, purge, hook, etc.)
- Setting up deployment pipelines for Rossum configurations
- Pulling or pushing Rossum objects (schemas, hooks, queues, workspaces, rules, labels, engines)
- Deploying configurations between environments using deploy files
- Configuring
prd_config.yaml, credentials.yaml, or deploy YAML files
- Using attribute overrides (static, regex with
/#/ separator, $prd_ref, $source_value)
- Debugging deployment or sync issues between environments
- Writing CI/CD pipelines that automate Rossum deployments
