Options reference

Project location

Use --root when the current working directory is not the project root. Explicit file and config paths override normal project discovery.

Paths should identify project-owned files. The CLI passes resolved locations to the runtime instead of loading authoring or task configuration itself.

Task selection

Commands that require a task also accept a positional name:

Use --all only with commands that support multiple tasks. Task order follows the resolved project configuration.

Safe execution controls

--dry-run is the safest review mode. It should not mutate project files, delete stale files, or execute configured commands.

--refresh requests fresh source and artifact resolution. It is useful when caches may be stale, but it does not bypass validation or file-safety policy.

Skip controls help isolate rendering from project command failures.

Output controls

Use compact JSON for scripts and pretty JSON for human inspection. JSON mode should preserve typed diagnostics and result structure rather than embedding formatted terminal text.

Verbose mode presents runtime lifecycle events. Events are observational and do not replace the final operation result.

Combining options

Option ownership

The CLI owns option spelling and argument parsing. The runtime owns what project resolution, validation, planning, generation, cache refresh, and command execution mean.