Skip to main content
Repo Task Proof Loop is a repo-local workflow skill for non-trivial coding tasks. It creates a durable task folder under .agent/tasks/<TASK_ID>/, installs project-scoped Codex and Claude subagents, updates repo guidance, and drives a strict loop: 
spec freeze → build → evidence → fresh verify → minimal fix → fresh verify

​
What it solves

Three problems make non-trivial coding tasks hard to track and audit:
  • Proof lives outside the repo. Results, test output, and screenshots disappear when a session ends.
  • Implementation and verification are mixed. The same agent that writes code also declares it correct, with no independent check.
  • Task state is opaque. Picking up a half-finished task requires reconstructing context from scratch.
Repo Task Proof Loop solves all three. Every artifact the workflow produces — spec, evidence, verdict, raw output — is committed inside the repository. Verification always runs in a fresh session that has not seen the implementation. And because every phase writes to a fixed set of files, any task can be resumed or audited at any point.

​
What it creates

Running init creates the following structure inside the target repository: 
.agent/tasks/<TASK_ID>/
  spec.md
  evidence.md
  evidence.json
  raw/
    build.txt
    test-unit.txt
    test-integration.txt
    lint.txt
    screenshot-1.png
  verdict.json
  problems.md

.codex/agents/
  task-spec-freezer.toml
  task-builder.toml
  task-verifier.toml
  task-fixer.toml

.claude/agents/
  task-spec-freezer.md
  task-builder.md
  task-verifier.md
  task-fixer.md
It also inserts managed workflow blocks into:
  • AGENTS.md
  • The repo’s Claude guide file: CLAUDE.md or .claude/CLAUDE.md
The managed blocks are replaced in place on re-run, so any user-authored content outside the block markers is preserved.

​
Compatibility

RequirementDetails
Python3.10 or later (for bundled scripts)
CodexProject skill at .agents/skills/repo-task-proof-loop/
Claude CodeProject skill at .claude/skills/repo-task-proof-loop/
The skill can be used with either tool independently, or with both on the same repository. The initialization script writes repo-local workflow files into the target repository, not into the skill directory.

Quick Start

Go from zero to a completed verified task as fast as possible.

Workflow

Understand the full spec-freeze → build → evidence → verify → fix loop.

Build docs developers (and LLMs) love

Get started for freeTalk to us