CLI flags¶
Reference page. The canonical CLI argument list lives in the framework source — this page is being authored to mirror it.
Argument definitions are at:
Most-used flags¶
| Flag | Default | Purpose |
|---|---|---|
--problem-file <path> |
required | Path to a ProblemSpec JSON file. |
--infra=<manual\|auto> |
manual |
Whether to enable Tier C infrastructure generation. |
--infer-infrastructure |
off | Run MCDA scoring to pick technologies when infrastructure_choices is omitted. |
--deterministic |
off | Pin all tiers to temperature=0 and route every LLM call through the response cache. Identical inputs return cached outputs on subsequent runs. |
--replicates <N> |
1 | Run the pipeline N times with different seeds; report mean ± stddev. |
--prompt-cache / --no-prompt-cache |
on | Toggle Anthropic prompt caching. |
--max-cost-usd <N> |
unbounded | Graceful exit when run cost exceeds N. |
--resume <run_dir> |
n/a | Resume a crashed run from its CHECKPOINT.json. |
--rebuild-dashboard |
n/a | Aggregate meta-evaluation-results/ into the static HTML dashboard. |
--custom-patterns <path> |
n/a | Load a custom-pattern manifest (see Extend). |
Architecture Recovery flags¶
The brownfield → Clean-Architecture inverse pipeline (see Agentic Architecture Recovery). Each phase is a standalone invocation.
| Flag | Default | Purpose |
|---|---|---|
--recover-from <dir> |
n/a | Ingest a project and emit a faithful recovered.squib + categorized violations.json. |
--language <python\|javascript\|typescript\|java> |
python |
Source language of the project to recover. |
--recover-out <path> |
recovered.squib |
Where to write the recovered Squib. |
--criteria <csv> |
all six | Architectural criteria, most-important first, driving the preserve-vs-split verdict (testability,simplicity,performance,evolvability,migration_safety,delivery_speed). |
--triage <violations.json> |
n/a | Interactively review the violations (opt-out per category) and write refactor_plan.json. |
--refactor <squib> |
n/a | Apply a --plan to a recovered Squib and emit the refactored Squib. |
--plan <refactor_plan.json> |
required with --refactor |
The triage decision to apply. |
--refactor-out <path> |
refactored.squib |
Where to write the refactored Squib. |
--squib-file <squib> |
n/a | Regenerate code from a signed-off Squib (short-circuits the architect). |
--legacy-tests <dir> |
n/a | Derive acceptance criteria from the brownfield project's test_* functions during regeneration. |
See also¶
- Get started — the canonical 5-step run.
- Verify a run — how to read what the CLI wrote.