mandatory-fill-inlisted

# Skill-3: Exclusive Structured Mandatory Fill-in Guidance Input: `agent_model` (e.g. `RIDE`) + `use_case` (e.g. `Salary_Negotiation`) + `filled_data` (JSON object of the user's card values) Output: strict JSON — `{ "action": "force_fill_batch", "missing_fields": [{"field": "...", "question": "..."}], "filled_fields": [...], "message": "..." }` **or** `{ "action": "ready_to_generate" }` ## Procedure 1. **Load the model's fill-in fields** — Read the `## Model reference` section in your agent instructions and extract the **Fill-in fields** table (or Read `config/model-reference.md` for the same table). Done when the field list and its guiding questions are in context; if the section is missing → stop, report `{"action": "error", "reason": "No fill-in fields defined for model <agent_model>"}`. 2. **Run the sufficiency gate** — For each field in the table, judge the corresponding value in `filled_data`: is it non-empty AND specific (names, numbers, dates, or concrete context — not placeholders or vague fragments)? Done when every field has a pass/fail verdict. 3. **If all fields pass the gate** — return `{ "action": "ready_to_generate", "message": "Validation passed — input is sufficient, no additional questions needed" }` — the input is sufficient to generate a sharp version. Done when the caller can hand off to Skill-7. 4. **If any field is missing or vague** — return `force_fill_batch` naming **ALL** failing fields at once, each with its guiding question from the model refe