adversarial-implementation

Task: $ARGUMENTS (If no task is provided, read TODO.md, if it exists. Implement the next incomplete subsection. If there is no TODO.md file, prompt the user for instructions.)

Adversarial Implementation Protocol

When implementing from TODO.md:

• Implementation unit: Individual checkboxes (keeps subagent sessions manageable)
• Completion unit (aka "subsection"): The immediate parent heading of a group of checkboxes -- i.e., the most specific heading that directly contains them, not any ancestor.

Example TODO structure:

### 3.1 OAuth Setup
#### 3.1.1 Configure provider
- [ ] Add client ID
- [ ] Add client secret
#### 3.1.2 Implement callback
- [ ] Handle redirect

Here, 3.1.1 and 3.1.2 are completion units (each is a subsection directly containing checkboxes). 3.1 OAuth Setup is NOT a completion unit -- it's a parent grouping.

A completion unit is complete only when ALL its checkboxes are checked -- including any that require human verification.

Isolated subagents

Whenever this guide says to invoke an isolated subagent, fall back to a general agent if the isolated subagent doesn't exist. In either case, use model 'opus' and effort 'low' for subagents unless otherwise instructed by the user.

Phase 1: Plan the Subsection

For the next incomplete Phase subsection:

1. Read ALL checkboxes within the subsection
2. Categorize each checkbox:
   • Automatable: Code changes, automated tests
   • Human-required: Browser interactions, visual verification, manual testing
3. Process automatable items one at a time (or in small logical batches) through Phases 2-4 before moving to the next item
4. Track which items are complete within the subsection
5. If subsection has NO automatable items, skip directly to Phase 6

Phase 2: Implement Single Item via Subagent

For each automatable checkbox:

1. Spawn an isolated task subagent (if one exists, or a general subagent otherwise) with this prompt structure:

   Task: [specific checkbox item]
   Context files: TODO.md, any other relevant specs or instructions (OMIT code
   files; the subagent can find these on its own)
   Constraints: [project rules, style guide refs]
   Acceptance criteria: [the specific checkbox, explicitly stated]
   Output: Implement and report a concise summary of what you changed.

1. Do NOT provide the full codebase -- give minimal necessary context so you minimize use of the main context. Include: TODO.md, relevant specs, file paths to modify. Exclude: file contents the subagent can read itself, unrelated modules.