Hazma

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.

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.

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.

Synthesize existing Hazma PR review feedback, assess each comment on merit, implement justified in-scope fixes, run the preflight gate, and provide verification-ready responses. Use when reviews already exist; do not use to collect reviews.

Orchestrate one Hazma project task end to end in a dedicated Codex worktree: resolve, implement, open a draft PR, run a bounded review cycle, and finalize or retain the PR draft. Use when a user asks to implement and ship one project task; it requires projects/<slug>/PLAN.md.

Branch, run the preflight gate, commit with Conventional Commits, push, and open a PR that follows the repo's PR guidelines and passes CI.

Execute exactly one task (or tightly related task cluster) from a project's PLAN, keep scope narrow, update the task note, run the preflight gate, and escalate only canonical plan changes into ADRs and plan files. Stops before commit — the caller (or /commit-and-pr) owns the commit.

Orchestrate the full PR review loop — select reviewers, spawn them in parallel, commit and push fixes, verify, post a round comment, and iterate to convergence or a cap. The single review-loop implementation; task-pipeline Phase D delegates here.

Stress-test a project plan under projects/<slug>/ before implementation starts, producing a findings-first review across feasibility, numerics, correctness, architecture, and idiomatic Python — read-only, no plan edits.

Review a PR that implements one plan task against its spec in projects/<slug>/, as a single lens-focused reviewer. Distinct from generic /code-review (working-tree diffs), /review-plan (pre-implementation plans), and /review-cycle (multi-reviewer orchestration).

As the implementer, synthesize existing PR review feedback from one or more reviewers, implement the justified fixes behind the preflight gate, and produce per-reviewer, verification-ready response summaries. Use when reviews already exist and you need to address them — not to collect reviews.

Orchestrate one project task end-to-end — resolve, implement, review, ship — delegating each phase to a context-isolated subagent over a shared worktree.