# Omagy Workflow Rules

Use `omagy state` for workflow state. Do not directly edit `.omagy/state` except through Omagy runtime commands.

Treat plugin-scoped slash prompts as workflow invocations, not as plain text.
If the prompt starts with `/omagy:ralph`, load the Ralph execution contract and
drive the runtime with `omagy ralph ...` commands. Do not answer that
`/omagy:ralph` is an unknown external system, and do not satisfy the request
only by running the requested verification command outside Ralph state.

Use `omagy plan` for PRD/test-spec planning artifacts. Planned execution must
derive from a matched `.omagy/plans/prd-<timestamp>-<slug>.md` and
`.omagy/plans/test-spec-<timestamp>-<slug>.md` pair; do not treat ambient notes
or stale markdown as execution handoff authority.

Plan-bound execution must pass `omagy plan handoff` before starting. For Team,
use `omagy team from-plan` so the approved PRD/test-spec context is stored in
team state and worker inboxes.