Problem Statement
When running commands like specify specify or specify plan, the CLI immediately invokes the AI model to generate output. For large projects or when iterating on constitution/principles, users may want to preview what the output would look like without burning tokens or waiting for generation — especially useful in CI environments or when testing templates.
Proposed Solution
Add a --dry-run flag to specify specify and specify plan commands. When enabled, the CLI prints the rendered prompt/inputs that would be sent to the AI without actually making the API call. This lets users verify their constitution, templates, and configuration are correct before spending time or money on actual generation.
Alternatives Considered
- Running in a separate sandboxed environment — heavyweight, impractical for quick iteration
- Checking generated output after the fact — wastes tokens on incorrect configurations
- Modifying templates blindly — error-prone without feedback
Component
Specify CLI (initialization, commands)
AI Agent (if applicable)
All agents
Use Cases
- When tuning constitution principles in CI, verify constitution is valid before running on a real project
- When authoring custom spec templates, preview the prompt that will be sent without making an API call
- When onboarding new team members, demonstrate the workflow without generating real output
Acceptance Criteria
Additional Context
Addresses token cost concerns in large teams and CI environments. Similar to how kubectl apply --dry-run works for Kubernetes manifests.
Problem Statement
When running commands like
specify specifyorspecify plan, the CLI immediately invokes the AI model to generate output. For large projects or when iterating on constitution/principles, users may want to preview what the output would look like without burning tokens or waiting for generation — especially useful in CI environments or when testing templates.Proposed Solution
Add a
--dry-runflag tospecify specifyandspecify plancommands. When enabled, the CLI prints the rendered prompt/inputs that would be sent to the AI without actually making the API call. This lets users verify their constitution, templates, and configuration are correct before spending time or money on actual generation.Alternatives Considered
Component
Specify CLI (initialization, commands)
AI Agent (if applicable)
All agents
Use Cases
Acceptance Criteria
--dry-runflag added tospecify specifycommand--dry-runflag added tospecify plancommandAdditional Context
Addresses token cost concerns in large teams and CI environments. Similar to how
kubectl apply --dry-runworks for Kubernetes manifests.