Menu
Implement a planned change under the Parallax write gate with friction-loop verification.
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.
Record a Parallax protocol checkpoint with concrete evidence before gated implementation work.
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 | build |
| description | Implement a planned change under the Parallax write gate with friction-loop verification. |
| argument-hint | [plan item or implementation goal] |
| user-invocable | true |
Use the current Claude session ID and call parallax_build. Before the first mutation, ensure ambiguity, invariants, and gate check-ins contain concrete evidence.
Implement $ARGUMENTS in the smallest coherent batches. Follow project instructions and nearby patterns; preserve public behavior unless the plan changes it. Validate trust-boundary input and handle relevant empty, failure, ordering, and compatibility cases.
After each mutation batch, read the native verification result. On failure, diagnose and fix the cause. Use parallax_verify for an explicit or thorough check when needed. Never weaken checks, bypass a denied write, or mutate after retries are exhausted.
Finish by reviewing the diff, running targeted tests, recording the commit decision and summary, and reporting changed files, verified behavior, commands, and residual risk.
