---
description: Start a project task by loading shared plan and progress context
argument-hint: [agent-or-task]
allowed-tools: [Read, Glob, Grep, Bash, Edit]
---

# /start-agent-work

Start work in this repository with the project coordination protocol.

## Arguments

The user invoked this command with: $ARGUMENTS

## Workflow

1. Read `PLAN.md` and `PROGRESS.md`.
2. State the current goal, the next action, and any blocker that matters for the task.
3. Read `docs/WORKARCHIVE.md` when historical completed-work context, previous verification, or sample conversion evidence is needed.
4. Read only the additional source documents needed for the requested work.
5. If subagents are useful and the user explicitly asked for delegated agent work, choose the smallest set of `.codex/agents/*.toml` roles that covers the task.
6. For substantial implementation work, use the harness sequence: `harness-planner-agent` drafts the plan and contract, `feature-generator-agent` implements one agreed chunk, and `evaluation-agent` reviews the contract and completed work.
7. Do not implement converter code unless the user explicitly requests implementation.
8. After meaningful changes, update `PROGRESS.md`; update `PLAN.md` only when sequencing, decisions, ownership, or blockers change.
9. Archive completed work in `docs/WORKARCHIVE.md` when it no longer needs to stay in `PROGRESS.md`.
10. Run the smallest useful verification, check git status, and commit project changes while excluding `samples/`.

## Guardrails

- Keep MinerU 3.1.0 as the only conversion engine.
- Allow MinerU 3.1.0's CLI-internal temporary local `mineru-api`, but prohibit `--api-url`, remote APIs, router mode, HTTP client backends, and remote OpenAI-compatible backends.
- Keep runtime processing local-only.
- Keep `samples/` out of commits unless the user explicitly requests otherwise.
- Prefer official sources for changing facts about Codex, MinerU, Python, uv, CUDA, or licenses.