Command reference
---
title: Command reference
description: Every Specgent pipeline operation, side command and administrative command.
---
## How commands are spelled
Packaged as the `specgent` plugin, commands use the plugin namespace, for
example `/specgent:idea-to-prd` or `/specgent:init`. A project-local install
spells workflow commands `/<name>` and administrative commands
`/specgent-<name>`. There is no single dispatcher command; the plugin namespace
is the command surface.
Every workflow command is invoked by hand and ends by stopping. No workflow
command invokes another.
## Pipeline operations
| Order | Operation | Result |
| ----- | -------------------------- | ----------------------------------------------------------------------- |
| 0 | `ingest-workspace-context` | versioned workspace context, evidence routes, authority classifications |
| 1 | `idea-and-research` | evidence-backed opportunity and research brief |
| 2 | `idea-to-prd` | one measurable PRD revision and requirements register |
| 3 | `review-prd` | independent verdict for the exact PRD revision |
| 4 | `prd-to-rfc` | one repository-grounded RFC revision for the accepted PRD scope |
| 5 | `review-rfc` | independent RFC verdict and technical-risk register |
| 6 | `define-epics` | outcome-oriented Epics derived from the accepted PRD and RFC |
| 7 | `define-features` | Features for one selected Epic |
| 8 | `specify-feature` | behavioral and technical contract for one selected Feature |
| 9 | `define-feature-slices` | explicit no-slice decision or actual Slice definitions |
| 10 | `specify-feature-slice` | deep technical contract for one selected Slice |
[The eleven operations](../guide/lifecycle.md) describes each one in order.
## Beside the pipeline
These commands declare their own outputs but add no lifecycle step.
| Command | What it does |
| ---------------------- | ------------------------------------------------------------------------ |
| `review-feature` | issues a verdict for one exact Feature Specification revision |
| `review-feature-slice` | issues a verdict for one exact Feature-Slice Specification revision |
| `refine-prd` | runs a decision session over a sealed PRD review |
| `refine-rfc` | runs a decision session over a sealed RFC review |
| `refine-feature` | runs a decision session over a sealed Feature Specification review |
| `refine-feature-slice` | runs a decision session over a sealed Feature-Slice Specification review |
[Reviewing and refining](../guide/review-and-refine.md) explains the loop they
form.
## Administrative commands
These commands operate the installation and add no lifecycle operation.
| Command | What it does |
| ------------------- | --------------------------------------------------------------------------------------------------- |
| `init` | bootstraps or repairs Specgent in a workspace, then reports what changed |
| `update` | refreshes the installed files at the current version |
| `upgrade` | moves a workspace to the distribution's version, backing up metadata and running forward migrations |
| `doctor` | diagnoses the installation; a check that cannot reach a verdict is undetermined, never a pass |
| `sync-context` | checks whether promoted workspace context is stale, and promotes a sealed candidate on approval |
| `register-artifact` | seals an externally authored document as an imported, citable revision |
| `reconcile-run` | recovers a workspace after a crashed run, repairing only what is deterministically recoverable |
| `erase-context` | deliberately removes one repository's context from the pool, recording the reason first |
`reconcile-run` is a dry run by default. `register-artifact` preserves the
source bytes exactly and reports which approvals the policy still requires.