Skip to main content
Use this guide when no initialized task exists yet and you want to create the repo-local proof folder, install subagents, and update workflow guidance before any implementation begins.

Start New Task prompt

Copy this prompt into your agent session, then replace ... with either Task file: <path/to/task-file.md> or the task text pasted on the following lines.
Use $repo-task-proof-loop to initialize a new repo-local task for the work below. Seed the task from this request, install or refresh the project-scoped subagents, update the managed workflow guidance, and stop after init completes. Do not start build yet.
...

Step-by-step initialization

1

Set SKILL_PATH

Set SKILL_PATH to the installed skill directory before running any CLI commands.
SKILL_PATH=.agents/skills/repo-task-proof-loop
2

Run init

Run init from the repository root. Provide either a task file or inline task text.
python3 "$SKILL_PATH/scripts/task_loop.py" init \
  --task-id feature-auth-hardening \
  --task-file docs/tasks/auth-hardening.md
The initializer will:
  • Resolve the repo root
  • Create .agent/tasks/<TASK_ID>/ with all required artifact files
  • Install project-scoped subagent files into .codex/agents/ and .claude/agents/
  • Insert or refresh managed workflow blocks in AGENTS.md and the repo’s Claude guide file
3

Confirm artifacts exist

After init completes, verify that the task folder and spec.md are present before continuing.
python3 "$SKILL_PATH/scripts/task_loop.py" status \
  --task-id feature-auth-hardening
You should see all entries under required_files_present set to true and .agent/tasks/feature-auth-hardening/spec.md present on disk.
4

Run Continue Existing Task

Once init is confirmed, proceed to build using the Continue Existing Task guide.
init always comes before build. Do not skip it or overlap it with freeze, build, evidence, verify, fix, or any child-agent spawning.

Guide file options

Control which guide files the initializer creates or updates with --guides:
ValueBehavior
autoPreserves existing guide files; creates the product-native guide when installing that product’s agents
agentsCreates or updates AGENTS.md only
claudeCreates or updates the Claude guide file only
bothCreates or updates both AGENTS.md and the Claude guide file
noneSkips guide file changes entirely
With --guides auto, the initializer ensures CLAUDE.md exists whenever Claude agents are being installed and AGENTS.md exists whenever Codex agents are being installed.

Subagent installation options

Control which project-scoped subagent sets are installed with --install-subagents:
ValueBehavior
bothInstalls Codex agents under .codex/agents/ and Claude agents under .claude/agents/ (default)
codexInstalls Codex agents only
claudeInstalls Claude agents only
noneSkips subagent installation

Example with options

python3 "$SKILL_PATH/scripts/task_loop.py" init \
  --task-id feature-auth-hardening \
  --task-file docs/tasks/auth-hardening.md \
  --guides auto \
  --install-subagents both

Build docs developers (and LLMs) love