npx workspai readiness --jsonEmit the release-readiness verdict, blockers, and evidence references as structured JSON.
Workspace Intelligence command
workspai readiness
Evaluate whether current workspace evidence satisfies release-readiness requirements and blockers.
- Category
- Workspace Intelligence
- Workspace Intelligence
- Yes
- Produced artifacts
- 1
- Related contracts
- 3
- Registration
- commander
- Registered options
- 4
Operational role
This purpose is versioned in the CLI runtime command surface. It is not inferred from page copy or a generic command template.
Evaluate whether current workspace evidence satisfies release-readiness requirements and blockers.
Canonical invocation
This invocation is derived from the runtime command surface. Commands with a registered intelligence execution include their canonical evidence-producing flags.
npx workspai readinessOperational variants
These flag or action variants are separately described by the runtime contract but remain part of this canonical command rather than separate command pages.
Runtime signature
Arguments, aliases, and options come from the versioned snapshot of the live Commander tree emitted by the CLI. Contract-declared delegated commands intentionally expose only their canonical invocation.
Arguments and aliases
Aliases: None
No registered positional arguments.
Options
- --workspace <path>
- --json
- --strict
- --skip-verify
Contract relationships
Capability contracts govern whether the command exists; artifact contracts govern the structured output it produces.
Produced artifacts
Artifacts are durable machine-readable outputs. Their schema, path, and producer relationship must remain stable across CLI, CI, IDE, MCP, and agent consumers.
| Artifact | Schema version | Contract |
|---|---|---|
| .workspai/reports/release-readiness-last-run.json | release-readiness-v1 | contracts/release-readiness.v1.json |
Operational interpretation
Run this command inside the scope documented by its category. Treat declared structured output, raw renderer modes, and generated artifacts according to their published media type; human terminal prose must not be parsed as a stable contract. Consumers must preserve schema version, provenance, freshness, and verdict semantics when forwarding the result.