Skip to content

Status Values & Enums

All accepted enum values across the Animus system. These values are case-insensitive on input and kebab-case on output unless otherwise noted.


Normalized Subject Status

Used by: animus subject list --status, animus subject status, animus subject update --status

ValueAliasesDescription
backlogtodoTask is in the backlog, not yet ready for work
readyTask is ready to be picked up
in-progressin_progress, inprogressTask is actively being worked on
blockedTask is blocked by a dependency or issue
on-holdon_hold, onholdTask is paused/held
donecompletedTask is complete
cancelledTask has been cancelled

Serialization: kebab-case (e.g., "in-progress", "on-hold")

Groupings:

  • Active: in-progress
  • Terminal: done, cancelled
  • Blocked: blocked, on-hold

Subject Priority Buckets

Used by: animus subject create --priority, animus subject update --priority

ValueDescription
p0Highest priority
p1High priority
p2Normal priority
p3Lower priority

Serialization: lowercase (e.g., "p1")


Requirement Priority (MoSCoW)

Used internally by the built-in requirements domain model and requirement-linked workflows.

ValueDescription
mustMust have (non-negotiable)
shouldShould have (important but not critical)
couldCould have (nice to have)
wontWon't have (explicitly excluded)

Serialization: lowercase (e.g., "must", "should")

Default: should


Requirement Status

Used internally by the built-in requirements domain model and requirement-linked workflows.

ValueDescription
draftInitial state, requirement is being drafted
refinedRequirement has been refined with details and criteria
plannedRequirement is planned for implementation
in-progressRequirement is being implemented (alias: in_progress)
doneRequirement is fully implemented
po-reviewAwaiting product owner review
em-reviewAwaiting engineering manager review
needs-reworkSent back for rework after review
approvedApproved through review process
implementedImplementation complete and verified
deprecatedNo longer relevant

Serialization: kebab-case (e.g., "in-progress", "po-review", "needs-rework")

Default: draft


Workflow Phase Decision Verdict

Used in: PhaseDecision.verdict, on_verdict routing in workflow YAML

ValueDescription
advancePhase succeeded; proceed to next phase or on_verdict target
reworkPhase needs rework; route back to the specified target phase
skipPhase should be skipped; jump to the specified target
failPhase failed fatally; terminate workflow or route to error handler

Serialization: lowercase (e.g., "advance", "rework")

Unknown verdict values are deserialized as a catch-all Unknown variant.


Workflow Phase Status

Used in: WorkflowPhaseExecution.status

ValueDescription
pendingPhase has not started
readyPhase is ready to execute
runningPhase is currently executing
successPhase completed successfully
failedPhase failed
skippedPhase was skipped

Serialization: snake_case (e.g., "pending", "success")


Merge Strategy

Used in: post_success.merge.strategy in workflow YAML

ValueDescription
mergeStandard git merge (default)
squashSquash merge into a single commit
rebaseRebase onto target branch

Serialization: lowercase

Default: merge


Batch on_error Policy

Used by: animus.workflow.run-multiple

ValueDescription
continueProcess all items regardless of individual failures
stopStop after the first failure; remaining items are marked skipped

Agent Action

Used by: animus agent control --action, animus.agent.control

ValueDescription
pausePause the running agent
resumeResume a paused agent
terminateTerminate the agent

See also: Workflow YAML Schema, Configuration, Exit Codes.

Released under the Elastic License 2.0 (ELv2).