loopify

Use when auditing a Loop Contract, trace, quality gate, or done claim — or when acting as the independent verifier that grades a loop's success claim and writes verdict.md.

Use when executing an existing Loop Contract by running checks, observing failures, patching, rerunning, updating the trace, and stopping only with evidence.

Use when converting a prose spec, PRD, README, issue, or goal prompt into a Loop Contract with requirements, checks, authority boundaries, stop rules, and trace requirements.

Use when creating, maintaining, auditing, or summarizing loop trace receipts that record checks, failures, patches, rationale, evidence, and stop reasons.

Use when seeding a repository with loop materials such as a goal prompt, Loop Contract, quality gate, trace template, acceptance checklist, and test skeletons.

Use when turning vague requirements into concrete automated checks, visual review gates, manual review items, acceptance tests, or quality-gate commands.

Use when adding Codex SDK scripts or templates as loop actuators for repair, review, context building, trace summarization, or meta-loop proposal steps.

Use when a loop is stuck, repeating failures, flaking, patching the wrong target, hitting an authority conflict, or burning turns without convergence.

Use when creating demo-ready loop seed projects with a normal app target, material pack, quality gate, acceptance tests, trace template, and presenter script.

Use when adding budgets, approvals, rollback plans, data/privacy limits, dependency policy, authority boundaries, and harness-change contracts to higher-risk loops.

Use after a loop completes to extract reusable lessons from the contract, trace, final diff, failures, useful checks, ambiguities, and rejected attempts.