anti-phase-skip

Files (3)

• SKILL.md
• openai.yaml · agents/
• procedure.md · references/

SKILL.md (first lines)

# Anti Phase Skip

Skipping a phase cycle is a critical delivery defect. It creates false DONE claims,
unmerged behavior, stale validation, open tracker state, abandoned WIP, and runtime
failures that green unit tests cannot expose.

Activate before changing tasks, advancing a plan phase, handing off, or claiming
completion. Read the `complete procedure` (skill file).

A phase cannot be DONE until implementation, real runtime, applicable native gates,
integration update, commit, push, approved and merged PR, post-merge runtime, zero
residue, and canonical tracker closure all have fresh evidence. Missing one step keeps
the same phase open, and no other phase or work starts beside it; incomplete work is
pushed only to a preservation ref. `rules/workflow/phase-admission-protocol.md` (rule
file) Laws 0 and 4 own both.

An external-token validation excluded before invocation is recorded as `NOT EXECUTED`,
not green, and does not become a missing phase step. If invoked, it is applicable and
any credential or runtime failure remains red.

Only an explicit operator decision may pause, reorder, or replace a phase. A failed
check, actionable review, open PR, pending approval, or merge conflict is work inside
the phase: fix, publish, revalidate, and continue through landing. Report and request
help only after every authorized correction is exhausted and the remaining condition is
external or requires new authority. During tracker suspension, create no substitute
tracker or ledger, preserve evidence only in separately authorized Git/PR/CI, and keep
closure unavailable.

From datacosmos-br/agents, MIT.

More from datacosmos-br/agents