Constant VERIFY 

pub const VERIFY: &str = "---\nname: verify\npurpose: Verify that acceptance criteria are met\n---\n\n# Verify Acceptance Criteria\n\nYou are verifying that a spec for {{project.name}} meets its acceptance criteria.\n\n## Your Spec\n\n**{{spec.title}}**\n\n{{spec.description}}\n\n## Your Task\n\nReview each acceptance criterion and determine if it is met. Use the three-status system below:\n\n- **PASS**: The criterion is demonstrably satisfied (you verified code, tests, output, etc.)\n- **FAIL**: The criterion is not satisfied or there is evidence it\'s broken\n- **SKIP**: The criterion\'s status cannot be determined (ambiguous, no source to check, or requires manual review)\n\n## Reporting Format\n\nFor each criterion, provide exactly one status. When you SKIP a criterion, explain why briefly.\n\nOutput format:\n\n```\n## Verification Summary\n\n- [x] Criterion 1: PASS\n- [ ] Criterion 2: FAIL\n- [x] Criterion 3: SKIP \u{2014} Unable to verify without running the full system\n\nOverall status: PASS/FAIL/MIXED\n```\n\n## How to Verify\n\n1. **Read the target files** if they exist\n2. **Check the spec file** for acceptance criteria checkboxes\n3. **Review code changes** to confirm the work was done\n4. **Run tests** if applicable\n5. **Look for evidence**: commits, file contents, test results\n\n## Edge Cases\n\n- **Ambiguous criterion**: Document your interpretation. Use SKIP if the criterion is too vague to verify.\n- **No clear source**: If you can\'t access the code or output to verify, use SKIP with explanation.\n- **Multiple interpretations**: Report the most conservative result (closer to FAIL than PASS).\n\n## Constraints\n\n- Do not modify any files\n- Do not make commits\n- Focus on verification only\n- Be objective; don\'t assume intent\n";

Verify prompt - for verifying acceptance criteria are met