{"id":"cx-agent-first-week-plan-table-rules","audience":"learning-development","category":"support-work","technique":"constraints","track":"support","level":"beginner","title":"Build a five-day onboarding table that follows the sequencing rules","free":false,"task":"Output a table with the header \"Day | Morning | Afternoon\" and five rows, Mon to Fri, following the rules. Plain text, each cell at most 6 words, under 90 words in all.","materialLabel":"Your material (attached to your prompt automatically)","material":"NEW AGENT WEEK-ONE RULES\n1. Day 1 is orientation (morning) and tools training (afternoon).\n2. Agents shadow a live agent twice before taking live tickets: one shadow session per half-day, and shadowing happens on days 2 and 3 only (two half-days on day 2 = morning, day 3 = morning).\n3. First live tickets start on day 3 afternoon, with a buddy checking each reply.\n4. Product knowledge sessions fill any remaining half-days on days 2 and 4.\n5. Friday afternoon is the QA review with the team lead. Friday morning is live tickets.\n6. No half-day can have two activities.\n\nNOTES\nThe trainer is out on Thursday morning, so no product knowledge session that morning. Thursday morning is live tickets with a buddy.","rules":[{"type":"plainText"},{"type":"maxWords","max":90}],"mistakes":[{"title":"Putting product knowledge on Thursday morning","why":"The AI ignores the trainer's absence.","fix":"Say: \"Thursday morning is live tickets; trainer is out.\"","checks":["r2"]},{"title":"Starting live tickets too early","why":"The AI starts live tickets on day 2.","fix":"Say: \"Live tickets start Wednesday afternoon.\"","checks":["r1"]},{"title":"Missing the table format","why":"The AI writes paragraphs by day.","fix":"Give the header and cell limit.","checks":["r0"]},{"title":"Getting markdown back","why":"AI adds bold and headings by default, which show up as stray symbols where this is pasted.","fix":"Say \"plain text, no bold, no headings, no asterisks\".","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and usually runs long, so a vague \"keep it short\" lands well over the limit.","fix":"Cap each part instead of the total, for example \"each line under 15 words\".","checks":["maxWords"]}],"promptHints":[{"label":"Gives the header","patterns":["day \\| morning \\| afternoon"]},{"label":"Limits cells","patterns":["6 words","at most 6","each cell"]},{"label":"Mentions the sequencing rules","patterns":["shadow","rules","buddy"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a length limit","patterns":["\\d+\\s*words","word (limit|count)","under \\d+"]}],"hint":"Give the header and the cell limit, and tell the AI to follow every rule including the Thursday note.","rubricLabels":["The first row is \"Day | Morning | Afternoon\" followed by five rows Mon to Fri with one activity in each cell","Mon is orientation then tools training; Tue is shadowing in the morning and product knowledge in the afternoon; Wed is shadowing in the morning and live tickets with a buddy in the afternoon","Thu morning is live tickets with a buddy and Thu afternoon is product knowledge; Fri morning is live tickets and Fri afternoon is QA review"]}