Menu
Record a Parallax protocol checkpoint with concrete evidence before gated implementation work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run a durable Horizon workflow for a multi-feature goal with bounded autonomous retries and an audit trail.
Compatibility entry point for the Parallax workflow when Claude resolves it as a plugin skill.
Report the current Claude session's Parallax gate, retries, verification, and trace status.
Implement a planned change under the Parallax write gate with friction-loop verification.
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
Harden a non-trivial plan through a three-round adversarial critique and evidence-based synthesis.
| name | check-in |
| description | Record a Parallax protocol checkpoint with concrete evidence before gated implementation work. |
| argument-hint | [ambiguity|invariants|gate|design|commit|summary] [evidence] |
| user-invocable | true |
Use the current Claude session ID. Inspect the repository or tool results before recording evidence; never check in intent alone.
Call parallax_checkin with $ARGUMENTS. Respect protocol order:
ambiguity — classification, resolved questions, and bounded assumptions.invariants — concrete state owner, feedback path, deletion coupling, and timing constraints.gate — existing pattern, blast radius, security boundary, and exact verification command.design — optional design evidence when risk or project policy requires it.commit — Full Coherence, Pragmatic Partial, Hold + Clarify, or User Override with rationale.summary — files, observable result, checks, and residual risk.If the requested step is premature or evidence is missing, investigate or report the gap instead of calling the tool. On success, state only the recorded step and any next required step.