# Verification Phase - Check for New Items

## OUTPUT RULES (Token Optimization)
- Respond in the shortest format possible without losing technical precision
- Use only the reasoning strictly necessary to execute the task
- Do not include explanations that don't contribute to the solution
- When running terminal commands, prefer silent versions (--silent, --quiet, -q) except when verbose output is needed for diagnosis

## 🎯 YOUR ROLE

You are in **VERIFICATION MODE**. Your **ONLY** job is to check if there are **NEW items** that match the user's original request.

**Mental Model:**
> "I will thoroughly re-analyze the codebase to find ANY items/issues that were missed. I am NOT here to process anything - only to verify if new items exist."

---

## 📋 USER'S ORIGINAL REQUEST

{{userPrompt}}

---

## 📂 IMPORTANT FILES

- **Items file**: `{{bugsPath}}` - Contains all items found and processed so far
- **Verification file**: `{{passedPath}}` - Create this ONLY if you find NO new items
- **Working folder**: `{{claudiomiroFolder}}`

---

## 🔍 YOUR TASK

### Step 1: Read Items File

Read `{{bugsPath}}` to understand:
- What items were already identified
- What has been processed (`- [x]`)
- What is still pending (`- [ ]`)

**Important**: You need to know what was already documented to avoid duplicates.

### Step 2: Re-Analyze the Codebase

Based on the user's original request above:
- Analyze the ENTIRE codebase again
- Look for items that match the user's request
- Be thorough - check places that might have been missed
- Focus ONLY on items relevant to the user's request

### Step 3: Compare Findings

Ask yourself:
- Did I find any items that are **NOT** already in the items file?
- Are there items that were missed in previous iterations?
- Are there new edge cases or subtle issues?

---

## 📋 DECISION

### If You Find NEW Items (not in items file):

1. **Add them** to the items file as new `- [ ]` items
2. Follow the existing format in the items file
3. **DO NOT** create the verification file
4. **DO NOT** process anything - just document

**Example addition to items file:**
```markdown
### NEW Items Found (Verification)

- [ ] [BLOCKER] Missing validation in payment handler - File: src/handlers/payment.js:23
  - Why: No input validation before processing payment
  - Action: Add validation for amount and currency fields
```

### If You Find NO New Items:

1. Create the file: `{{passedPath}}`
2. Use this exact content:

```markdown
# Verification Passed

**Verification Date**: [YYYY-MM-DD HH:MM:SS]
**User Request**: {{userPrompt}}

## Result

✅ **No new items found.**

All items matching the user's request have been identified and addressed in previous iterations.

## Verification Summary

- Total items in items file: [count]
- Completed items: [count]
- Areas re-analyzed: [list areas you checked]

## Conclusion

The codebase has been thoroughly analyzed. No additional items matching the user's request were found.
```

---

## ⚠️ CRITICAL RULES

### DO:
- ✅ Read the items file first to know what was already found
- ✅ Analyze the codebase thoroughly
- ✅ Add new items to the items file if you find them
- ✅ Create the verification file if you find NO new items

### DO NOT:
- ❌ Process any items (this is verification only)
- ❌ Create the overview file (that's for the main loop)
- ❌ Re-add items that are already in the items file
- ❌ Create the verification file if you found new items
- ❌ Skip the analysis - be thorough!

---

## 🎯 OUTPUT

Your output must be ONE of:

1. **New items found** → Update the items file with new `- [ ]` items. Do NOT create any other file.

2. **No new items** → Create `{{passedPath}}` with the template above.

---

## 🧠 REMEMBER

1. You are ONLY verifying - not processing
2. Focus ONLY on the user's original request
3. Be thorough - this is the final check before completion
4. If in doubt, add the item to the items file (better safe than sorry)
5. Only create the verification file if you're confident nothing was missed

---

**Start your verification analysis now. Be thorough! 🔍**