القائمة
Safely determine whether a phased Hazma project can begin its next or a requested phase, then produce a guarded Codex kickoff prompt. Use when a user asks which phase is ready, asks to begin a phase, or needs a phase handoff; this skill does not implement the task.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Prepare a guarded, ready-to-paste kickoff prompt for the next eligible phase of a phased project, verifying strict prerequisite closeout first and refusing blocked or ambiguous phase starts.
Run Hazma's preflight gate, create or validate a Codex branch, commit intentionally with a valid Conventional Commit header, push, and open or update a pull request. Use when a user asks to commit, ship, or open a PR for current work.
Implement exactly one numbered task from a Hazma project plan, including task-note updates, numerical-impact measurement, documentation consistency, and the preflight gate. Use when a user asks to take a project task or the next project task; stop before committing unless the caller expressly owns the commit.
Orchestrate a bounded, multi-agent Codex review loop for a pushed Hazma pull request: select independent reviewer lenses, collect reviews in parallel, apply and push justified fixes, verify them, post durable round summaries, and stop at convergence, escalation, or the iteration cap.
Perform a read-only, findings-first review of a Hazma project PLAN before implementation, covering feasibility, numerical correctness, architecture, Python conventions, and testability. Use when a user asks whether a project plan is ready or asks to review projects/<slug>/PLAN.md.
Review a Hazma pull request against its project task or ad-hoc scope using one focused lens: generalist, completeness, logic, document consistency, or numerics. Use when a user asks for a PR review or when a Codex review cycle assigns a single reviewer lens.
| name | begin-phase |
| description | Safely determine whether a phased Hazma project can begin its next or a requested phase, then produce a guarded Codex kickoff prompt. Use when a user asks which phase is ready, asks to begin a phase, or needs a phase handoff; this skill does not implement the task. |
Prepare a handoff only. Do not edit project files or start implementation.
Resolve --project <slug> from an explicit argument or a project branch
(claude/ and codex/ both parse). Read projects/<slug>/PLAN.md and
refuse non-phased projects; direct those to $execute-single-task.
Map an optional completed phase to --completed-phase and a requested one
to --target-phase, then run the readiness oracle from the repository root:
python3 scripts/agents/resolve_phase.py --project <slug> --agent codex \
[--completed-phase <id>] [--target-phase <id>]
Follow its JSON result exactly:
ready: state why it is eligible and paste prompt verbatim in a fenced
block. It directs the next agent to $execute-single-task, requires a
re-check, and specifies a codex/ worktree.choose: list each eligible choice and its reason, then stop for the
user's selection.blocked: explain each blocker. A missing learning document means a
prerequisite is marked complete but was not closed out; (none) means no
phase remains in Not started state.error: report the message and request corrected input when needed.Never infer readiness by hand, choose among parallel phases automatically, or
generate a prompt for a blocked phase. Ignore _template.md files.