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.yamlmetadata and behavior flagsdraft.mddraft-stage promptfinalize.mdfinalize-stage prompt (when applicable)
Listing and selecting presets
List all presets:
List workflows in a specific preset:
Use a different preset for one invocation:
Running workflows by ID
run executes any workflow ID from the active preset and accepts either hyphenated or underscored IDs.
Two-phase flow contract
Many workflows use a two-phase contract:
draftstage produces an editable artifact.Human feedback is collected.
finalizestage 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:
ideationuxr-synthstrategic-reviewroadmappersprint-planningissueandloopimplementation pathscode-reviewretrospective
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-runbefore introducing a workflow in CI.Use
tracker-matrix --jsonwhen generating matrix jobs from tracker issues.Prefer explicit preset selection in scripts to avoid ambiguity.