caretta Help

Workflow and presets

caretta is workflow-first. Most operations are executed as reusable workflows shipped in preset directories.

Where workflows live

  • Bundled workflows: assets/workflows/<preset>/

  • Typical files per workflow:

    • workflow.yaml metadata and behavior flags

    • draft.md draft-stage prompt

    • finalize.md finalize-stage prompt (when applicable)

Listing and selecting presets

List all presets:

caretta presets

List workflows in a specific preset:

caretta presets default

Use a different preset for one invocation:

caretta --preset xp ideation

Running workflows by ID

run executes any workflow ID from the active preset and accepts either hyphenated or underscored IDs.

caretta run backlog-curation caretta run backlog_curation

Two-phase flow contract

Many workflows use a two-phase contract:

  1. draft stage produces an editable artifact.

  2. Human feedback is collected.

  3. finalize stage integrates feedback and publishes final output.

With --auto, caretta can synthesize stand-in feedback for supported flows and continue directly to finalize.

Lifecycle actions in default project loop

Typical long-cycle project operations include:

  • ideation

  • uxr-synth

  • strategic-review

  • roadmapper

  • sprint-planning

  • issue and loop implementation paths

  • code-review

  • retrospective

These actions form a repeating strategy-to-execution loop with artifacts moving through issues and pull requests.

Out-of-loop hygiene workflows

refresh-docs and refresh-agents are maintenance actions. They are not part of the strategic lifecycle loop but keep project collateral and agent-related assets in sync.

Advice for automation use

  • Use --dry-run before introducing a workflow in CI.

  • Use tracker-matrix --json when generating matrix jobs from tracker issues.

  • Prefer explicit preset selection in scripts to avoid ambiguity.

Last modified: 02 July 2026