---
name: evaluate-submission
description: Run a full TAM partnership business-evaluation on a WooCommerce Marketplace submission thread — thread analysis, missing-info detection, 6-dimension fit scoring with adversarial self-check, response drafting, and (when applicable) strategy guidance + follow-up handling. Use when a TAM needs the yes/no/maybe call on a new submission.
allowed-tools:
  - Read
  - Edit
  - Write
  - Grep
  - Bash
argument-hint: "[pasted submission thread or path to a file containing the thread]"
---

Run a complete business-fit evaluation on a WooCommerce Marketplace payment submission thread.

`$ARGUMENTS` is either pasted thread text **or** a filesystem path to a file containing the thread.

## Workflow

0. **Resolve the input:**
   - If `$ARGUMENTS` is empty, stop and ask the TAM: "Paste the submission thread, or pass a path to a file containing it (e.g. `/evaluate-submission ~/threads/acme-pay.txt`)." Do not proceed.
   - If `$ARGUMENTS` looks like a path (starts with `/`, `~`, or `./`, or matches a file on disk), Read that file and use its contents as the thread.
   - Otherwise treat `$ARGUMENTS` as the thread text itself.

1. **Load the workflow** — Read `workflows/submission-evaluation-workflow.md` and follow it end-to-end. Execute Steps 1–8 autonomously (Tier 1 + Tier 2). Stop at Step 9 for TAM verification.

2. **Load the skills as you go:**
   - Step 1 → `skills/business-review/submission-thread-analyzer.md`
   - Step 2 → `skills/business-review/missing-info-detector.md`
   - Step 3 → `skills/business-review/partnership-fit-evaluator.md`
   - Step 3.5 → `agents/_shared/rubrics/adversarial-review.md` (Lightweight Mode by default; Full path for high-stakes calls per the workflow)
   - Step 4 → `skills/business-review/tam-response-generator.md`
   - Step 5 (conditional) → `skills/business-review/marketplace-strategy-advisor.md`
   - Step 6 (conditional) → `skills/business-review/followup-manager.md`
   - Policy reference → `context/woo-marketplace-policies.md`

3. **Save the report** — In Step 7, write the full package to `reviews/_submissions/<company-slug>/<YYYY-MM-DD>-evaluation.md`. Slug rules:
   - Kebab-case the company name; strip legal suffixes (Ltd, Inc, GmbH, S.A., LLC, etc.) and punctuation.
   - If the company already exists as a registered partner in `context/extension-registry.yml`, use that existing partner slug instead.
   - Create the directory if it doesn't exist.

4. **Capture the learning** — In Step 8, surface the structured fields (partner, interaction_type=`submission_triage`, outcome, key_signals_present, key_signals_missing, policy_blocker, fit_score) and remind the TAM that `python3 scripts/learnings.py capture` is the canonical command. (You can pre-format the JSON payload for them, but the actual append is the TAM's call.)

5. **Emit the final package** — Use exactly this output template (omit sections 5 and 6 when not applicable):

```
═══════════════════════════════════════════
  WOOCOMMERCE PARTNERSHIP EVALUATION
═══════════════════════════════════════════

## 1. Submission Summary
[Step 1 output]

## 2. Missing Information
[Step 2 output]

## 3. Partnership Fit Score
[Step 3 output, post-adversarial — note any adjustments from Step 3.5]

## 4. Draft TAM Response
[Step 4 output]

## 5. Strategy Guidance (if applicable)
[Step 5 output, or omitted]

## 6. Follow-up Response (if applicable)
[Step 6 output, or omitted]
```

6. **Tier 3 callout** — End the response with:

> **TAM: verify the report and decide whether to send the drafted response. TAMMIE will not send.** Cross-reference the Status-Mapping Table in `workflows/submission-evaluation-workflow.md` to choose between Reject / On Hold / Business Negotiation. If the outcome is partnership-eligible, update `context/deals-pipeline.yml` with a tracking entry.

Provide progress updates as each step completes. This is a long-running operation — surface the Submission Summary as soon as Step 1 lands so the TAM has early visibility.