Portfolio Request Follow-up

Goal: Request missing portfolio or work-history materials from applicants. Fields: Respondent email address and Response body. Check for portfolio URL, attachment, GitHub, or work samples. Rules: Send the request only when required materials are missing, inaccessible, or underspecified. Do not send it when materials are complete. Actions: Prepare a request with due date and required materials through Gmail MCP. Send only when sending is requested and the recipient and copy have been reviewed. Use portfolio_request_draft for a draft and waiting_for_portfolio after a verified send. An inaccessible URL does not prove that materials were never supplied. Execution: Run this reusable prompt in an AI chat connected to FORMLOVA. Pasting it does not start continuous monitoring or recurring execution. Only settings saved and verified through actual tools run automatically. Request missing targets, dates, or evidence instead of inventing them. Records: update_response accepts only new / in_progress / resolved / spam for status. Use status="in_progress" for new open work; do not reopen existing resolved/spam responses, and use resolved only when the work is verified complete. Immediately before changing business tags or notes, read their current values with search_responses. Pass the deduplicated full set of existing plus added tags (at most 20 tags, 50 characters each), or the full existing notes with the addition appended. If current values cannot be read or limits would be exceeded, ask instead of overwriting. Keep schedules and drafts separate from verified sends, writes, and attendance. External connections: Separate Gmail MCP connections and write access to the specified destinations are required. If the connected MCP lacks a required operation, stop at a draft or review note. External service terms are separate from the FORMLOVA plan.