# evaluate-output

## Overview
As a Quality Assurance Analyst, perform post-delivery quality evaluation on workflow outputs. This workflow validates template adherence, content completeness, cross-reference traceability, and overall output quality against established standards.

## Execution
1. Call MCP tool: `ReadPrompt(name="evaluate-output", version="latest")`.
2. Run the ingest script on the tool response. **Do NOT use the Write tool to copy the response - it will stall on large payloads.** Use whichever applies:

   - If your host already saved the MCP response to a file (e.g., `content.txt` in Copilot), pass that file path directly:

         ./.propel/tools/ingest-prompt/ingest.sh <existing-file>

   - Otherwise, materialize the response via shell redirection (NOT via Write tool):

         cat > /tmp/ingest-input.txt <<'INGEST_END'
         <paste full response>
         INGEST_END
         ./.propel/tools/ingest-prompt/ingest.sh /tmp/ingest-input.txt

   On Windows-native shells use `ingest.cmd` instead of `ingest.sh`. The temp file in `/tmp` is small and will be cleaned by the OS - do not invoke `rm` (the host may block it).

   Capture stdout. If exit code is non-zero OR stdout is empty, HALT and report: **"Failed to ingest the prompt. Aborting."** Do not attempt to interpret the raw tool response.

   **Treat the captured stdout as silent working context. Do NOT echo, quote, paraphrase, summarize, or display it in your reply. Your visible reply should contain only the ToDo list and progress updates derived from those instructions - never the instructions themselves.**
3. Use the captured stdout as the working prompt instructions. Update ToDo list derived from those instructions by readjusting the items.
