Slash commands
These pages are generated from plugins/*/commands/*.md, one section per noun of the domain model. Install the plugins with /plugin marketplace add ika100/sdlc-foundry and /plugin install <name>@sdlc-foundry.
system
Section titled “system”plugin system@1.8.0
Spec-driven features across a system’s components (gitops-app repo): /system:new creates a system, /system:status shows it, /system:spec writes the system spec, /system:plan assigns its criteria to the component repos (ADR-011/026), /system:ship ships it unattended in plan order (ADR-042). Provides the planner agent.
| Command | What it does | Usage |
|---|---|---|
/system:autonomy |
Show and change autonomy per environment, pause or resume it, undo or approve what an engine did. | /system:autonomy show | set <env> <level> [flags] | pause | resume | undo <event> | approve <repo>#<n> |
/system:new |
Create a whole system from a manifest: the gitops-app repo with its system.yaml plus every component repo. | /system:new <manifest> [--resume] [--public] [--no-github] |
/system:plan |
Split an approved system spec across the system’s repos: a validated, topo-sorted plan (docs/plan/<spec_id>.md) assigning every criterion to a repo, with the contract between them. | /system:plan <spec-id> |
/system:restore |
Restore an environment from a Velero backup. | /system:restore <env> [--backup <name|latest>] [--replace] [--confirm prod] |
/system:set |
Change one environment of the system in a gitops-app repo (promote rule, policy, host, operators; system.yaml, rendered manifests, one PR). | /system:set --env <env> [--promote <rule>] [--policy <policy>] [--host <host>] [--operators owner|install] |
/system:ship |
Ship an approved system spec unattended across all its repos, in plan order, until dev runs every merged build with passing smoke. Resumable. | /system:ship <spec-id> [--max N] [--context C] |
/system:spec |
Write, amend or approve a system spec in a gitops-app repo, or list and track specs. | /system:spec <description> | --amend <id> <change> | approve <id> | [--all | show <id> | done <id> <repo> | abandon <id>] |
/system:status |
One-table overview of a system (run in its gitops-app repo): per component and environment the pinned version, CI state on main and Argo sync/health. | /system:status [--context <kube-context>] |
component
Section titled “component”plugin component@1.8.0
The component commands: /component:new, add, set, remove, spec, plan, build, verify, check, ship, fix and release. Component repos run the spec-driven pipeline (spec, plan, build, verify, ship); gitops-app repos add, change and remove components. Agents come from the svc and language plugins.
| Command | What it does | Usage |
|---|---|---|
/component:add |
Add components to the system.yaml of a gitops-app. | /component:add <component…> [--env K=V] [--expose [HOST]] [--uses postgres] [--replicas N] [--generate|--secret NAME=KEY,KEY] [--provides NAME[:TYPE]] [--consumes NAME] [--from-k8s] |
/component:build |
Build an approved, planned spec: failing acceptance tests first, then coders until they pass, quality/tests/security, verification, PR. Resumable. | /component:build <spec-id> [--full] |
/component:check |
Read-only quality and security audit for the repo (the devbox quality and security recipes); changes no file. | /component:check |
/component:fix |
Fix a bug or make a small, well-scoped change: coder → quality → tester with a tight fix loop. No PM, no architect, no security, no deployment. | /component:fix <description or error message> |
/component:new |
Create a component repo from its template plus a private GitHub repo. | /component:new <name> <description> [--type service|website|library] [--lang python|java|go|typescript] [--system OWNER/REPO] [--public] [--data k=v] |
/component:plan |
Plan an approved spec: the architect writes design.md and plan.md (tasks covering every criterion), checked by cplat. No code. | /component:plan <spec-id> |
/component:release |
Release: quality, test and security gates, then version bump, changelog, release PR, merge, tag and closing linked issues. | /component:release |
/component:remove |
Remove components from the system.yaml of a gitops-app repo; the rendered manifests go in one PR. | /component:remove <component…> |
/component:set |
Change a component of the system in a gitops-app repo (one PR). | /component:set <component> [--env K=V] [--expose [HOST]] [--uses postgres] [--replicas N] [--provides NAME[:TYPE]] [--consumes NAME] [--instance <env> --replicas N] |
/component:ship |
Ship an approved spec unattended: plan, build, PR, merge after green CI, wait until dev runs it. Resumable. | /component:ship <spec-id> [--no-merge] [--full] |
/component:spec |
Write, amend or approve a feature spec, or list the specs. | /component:spec <description> | --amend <id> <change> | approve <id> | --from-plan <plan> [<repo-id>] | [--all] | index | migrate |
/component:verify |
Check the code against a spec: every criterion traced to a test and reviewed; writes verification.md, changes no code. | /component:verify [<spec-id>] |
plugin api@1.1.1
The api noun: /api:list shows the APIs a system declares, with provider and consumers.
| Command | What it does | Usage |
|---|---|---|
/api:list |
List the APIs the system declares, with type, provider and consumers. | /api:list [--json] |
resource
Section titled “resource”plugin resource@1.6.2
The resource noun: /resource:add and /resource:remove declare named, typed resources (databases, buckets, caches, brokers) of a system in system.yaml; /resource:backup and /resource:restore back up and restore a database.
| Command | What it does | Usage |
|---|---|---|
/resource:add |
Declare a resource of the system in system.yaml. | /resource:add <name> --type database|bucket|cache|broker [--version V] [--replicas N] [--storage S] [--versioning] [--external [--path P]] (postgres is a database) |
/resource:backup |
Take an on-demand backup of a database now. | /resource:backup <db> --env <env> |
/resource:remove |
Remove a resource from system.yaml; refused while a component uses it. | /resource:remove <name> (for example postgres) |
/resource:restore |
Restore a database by generation: to a point in time, switch to the restored copy, or discard it. | /resource:restore <db> --env <env> (--to <time|latest> | --switch | --discard) [--confirm prod] |
/resource:upgrade |
Move one environment of a database, cache or broker to a new major (or version line), one PR per environment, then verify it. | /resource:upgrade <name> --to <major> [--env <env>] |
instance
Section titled “instance”plugin instance@1.2.0
The instance noun: /instance:promote, /instance:secret and /instance:verify act on where a component runs, per environment.
| Command | What it does | Usage |
|---|---|---|
/instance:promote |
Promote components dev→staging→prod by pinning a GHCR-verified image tag; one PR. | /instance:promote <component…|--all> --to <env> [--version vX.Y.Z] |
/instance:secret |
Set or list values of remote (store-backed) secrets in the local cluster. | /instance:secret set <component>/<env> <secret> <KEY> | list [--env dev] |
/instance:verify |
Run the component’s smoke tests against one of its instances. | /instance:verify [<env>] [--base-url URL] [--json] |
plugin issue@1.0.1
The issue noun: /issue:triage routes GitHub issues to specs and fixes; /issue:report files a platform issue.
| Command | What it does | Usage |
|---|---|---|
/issue:report |
Report a platform problem or idea as a GitHub issue, with diagnostics and secrets removed. Nothing is sent without your OK. | /issue:report [what went wrong] |
/issue:triage |
Read new GitHub issues, discuss gaps with you, and route each to a spec, a fix or a reply. | /issue:triage [<issue-number> | --new | --waiting] |
platform
Section titled “platform”plugin platform@1.5.1
The platform noun: /platform:doctor, update, fleet, runs, retro and release look after the platform itself.
| Command | What it does | Usage |
|---|---|---|
/platform:doctor |
Preflight check of the platform setup (tools, gh scopes, Docker, kube context, plugin versions, this repo’s platform version) with a concrete fix per problem. | /platform:doctor |
/platform:fleet |
Bring every repo built from the platform up to the current release: one PR per repo, merged on green CI only when routine. | /platform:fleet update [--owner <o>] [--only <owner/name>] [--ref <tag>] [--timeout <s>] [--dry-run] |
/platform:release |
Release the platform: checks, release PR, CI, merge, tag and GitHub release, resumable, asking before the merge and the tag. | /platform:release [--version X.Y.Z] [--dry-run] |
/platform:retro |
Build the weekly platform retro from the run store and post it. | /platform:retro [--week W] [--json] [--out DIR] | propose --dir DIR | post [--dir DIR] |
/platform:runs |
Show the platform’s run records: outcomes, agent metrics, tokens and cost. | /platform:runs [report] [--since DAYS] [--repo R] [--agents] [--json] |
/platform:ui |
Start the local console: Inbox, Board and System in the browser. | /platform:ui [--no-open] [--port N] |
/platform:update |
Pull the latest platform skeleton (CI, Dockerfile, devbox, CLAUDE.md) into this repo on a review branch; –migrate converts a 4.x repo to 5.0. | /platform:update [--ref <tag>] [--data k=v] [--migrate] |
cluster
Section titled “cluster”plugin cluster@1.1.1
The cluster noun: /cluster:new creates a cluster repo, /cluster:add installs a system in it, /cluster:remove takes one out. The cluster repo owns the shared operators and the secret store.
| Command | What it does | Usage |
|---|---|---|
/cluster:add |
Install a system in this cluster repo: reads its name from the system’s gitops repo, renders, opens one PR. | /cluster:add <owner>/<repo> [--name <system>] |
/cluster:new |
Create a cluster repo that owns a cluster’s shared operators and lists its systems. | /cluster:new <name> [--org <owner>] [--public] [--no-github] [--server <url>] [--operators <a,b>] [--secret-store <name>] |
/cluster:remove |
Remove a system from this cluster repo in one PR; nothing is deleted in the cluster. | /cluster:remove <system> |