Case Packet
Purpose
Terminal artifact: the complete case packet on first touch - the retail equivalent of the NCR.
When to use
- End of every return case, once
governed.json exists; or when asked for the customer response or manager exception draft.
When NOT to use
- A case that has not been through eligibility-check (no
eligibility block) - run the chain first; do not decide here.
- Starting a case from raw desk facts - return-intake.
- Policy questions - policy-retrieve. Non-return write-ups (incidents, safety, HR) - other plugins.
Where the data comes from
This plugin ships no sample data. The packet template (references/case-packet-template.md) and policy text (references/returns-rules.md) are configuration inside this skill folder. The case is the user's own content:
governed.json written earlier in the session by eligibility-check, or a governed case file the user names, links or attaches in the chat.
- Their OneDrive or SharePoint, found with Work IQ search (Microsoft 365 search) by case ID or file name when no location is given.
- The original service-desk note or customer email (for the customer's stated context in an exception request), found the same way.
Read each source with the file reader (ReadFileContent) and cite it by file name and row or line. Write the packet (CASE-<case_id>.md) to the session working folder, never into the plugin. If governed.json cannot be found, say so and ask the user where it is (or run the chain first). Never invent case facts or fall back to example values.
Inputs
Configuration ships inside this skill folder (synced from the plugin-root shared/ copy before packaging): config/, contracts/, references/ - paths below are relative to this skill folder.
governed.json (full payload, from eligibility-check in this session or the user's file - see Where the data comes from) + references/case-packet-template.md + references/returns-rules.md.
Steps
- Validate
governed.json against the contract; escalations and fraud-signal holds lead the packet.
- Fill references/case-packet-template.md section by section: cited case facts, reason code (+ ambiguity note), determination + clause, recommendation, missing-evidence list, factual fraud signals, customer response draft in the template's tone, and the manager exception-request draft only when the customer asked for one (#5.1).
- Every
<slot> is filled from the payload, policy text or config, or written as not on record. No angle-bracket or square-bracket placeholders remain.
- Mark DRAFT with the sign-off block - a human authorises any refund, exchange or decline.
Example
User: "Build the case packet for RET-2000-00001; the customer asked for a goodwill exception."
-> read governed.json (ineligible RET-2.1, hold_for_review, 2 signals) + references/case-packet-template.md
-> fill sections 0-9; section 8 (manager exception request) included because the customer asked
-> customer draft: policy outcome + clause + next step; no mention of signals; no timings
Reply: "CASE-RET-2000-00001.md drafted (DRAFT). Routing: hold_for_review -> Asset Protection. Determination: ineligible, RET-2.1.
Customer response and manager exception request drafted; decision block left for the manager."
Output format
CASE-<case_id>.md following the template's numbered sections 0-9. In chat: routing line, determination + clause, recommendation, signal count, and the two drafts' status.
Grounding requirements
Every claim cites order, receipt, history, clause or config. Customer-facing text states only what policy text and the record support - no processing times, refund timings or goodwill promises unless quoted from policy text (#5.0).
Guardrails
- Never fabricate facts, timings, approvals or review outcomes; every claim cites the payload, policy text or config.
- Never authorise a refund, release funds, adjudicate fraud, dispose inventory, book a carrier, or send the response to the customer (plugin boundary).
- Signals appear as signals in the internal sections only; the customer response never mentions suspicion, fraud or asset protection.
- Never state that asset protection or a manager has reviewed or cleared anything unless the payload records it.
- Never fill the manager's decision block.
Escalation / uncertainty
If governed.json lacks an eligibility block, stop and route the case back through eligibility-check - never decide here. If a template slot has no source, write not on record; never fabricate a value to fill it.
hold_for_review packets route to asset protection with the signal citations attached; missing payload fields are written as not on record and listed under Missing evidence.
1---2name: case-packet3description: 'Drafts the return case packet - determination, recommendation, evidence list, fraud signals, customer response draft, manager exception request - from the governed contract payload using the packet template. Use to close every return case: "build the case packet", "write up the return", "draft the customer response", "draft the manager exception request", "close the return case". Do NOT use to start a case - use return-intake instead; not for eligibility or red flags - use eligibility-check; not for incident or safety write-ups.'4license: Proprietary5metadata:6 source: https://skillmd.com/skills/microsoft/case-packet7 version: 1.0.48 author: Microsoft Retail & CPG Skills9 category: writing10 icon: DocumentEdit11---1213# Case Packet14## Purpose15Terminal artifact: the complete case packet on first touch - the retail equivalent of the NCR.16## When to use17- End of every return case, once `governed.json` exists; or when asked for the customer response or manager exception draft.18## When NOT to use19- A case that has not been through eligibility-check (no `eligibility` block) - run the chain first; do not decide here.20- Starting a case from raw desk facts - return-intake.21- Policy questions - policy-retrieve. Non-return write-ups (incidents, safety, HR) - other plugins.22## Where the data comes from23This plugin ships no sample data. The packet template (references/case-packet-template.md) and policy text (references/returns-rules.md) are configuration inside this skill folder. The case is the user's own content:24- `governed.json` written earlier in the session by eligibility-check, or a governed case file the user names, links or attaches in the chat.25- Their OneDrive or SharePoint, found with Work IQ search (Microsoft 365 search) by case ID or file name when no location is given.26- The original service-desk note or customer email (for the customer's stated context in an exception request), found the same way.2728Read each source with the file reader (ReadFileContent) and cite it by file name and row or line. Write the packet (`CASE-<case_id>.md`) to the session working folder, never into the plugin. If `governed.json` cannot be found, say so and ask the user where it is (or run the chain first). Never invent case facts or fall back to example values.2930## Inputs31Configuration ships inside this skill folder (synced from the plugin-root shared/ copy before packaging): `config/`, `contracts/`, `references/` - paths below are relative to this skill folder.32`governed.json` (full payload, from eligibility-check in this session or the user's file - see *Where the data comes from*) + references/case-packet-template.md + references/returns-rules.md.33## Steps341. Validate `governed.json` against the contract; escalations and fraud-signal holds lead the packet.352. Fill references/case-packet-template.md section by section: cited case facts, reason code (+ ambiguity note), determination + clause, recommendation, missing-evidence list, factual fraud signals, customer response draft in the template's tone, and the manager exception-request draft only when the customer asked for one (#5.1).363. Every `<slot>` is filled from the payload, policy text or config, or written as `not on record`. No angle-bracket or square-bracket placeholders remain.374. Mark DRAFT with the sign-off block - a human authorises any refund, exchange or decline.38## Example39```40User: "Build the case packet for RET-2000-00001; the customer asked for a goodwill exception."41-> read governed.json (ineligible RET-2.1, hold_for_review, 2 signals) + references/case-packet-template.md42-> fill sections 0-9; section 8 (manager exception request) included because the customer asked43-> customer draft: policy outcome + clause + next step; no mention of signals; no timings44Reply: "CASE-RET-2000-00001.md drafted (DRAFT). Routing: hold_for_review -> Asset Protection. Determination: ineligible, RET-2.1.45 Customer response and manager exception request drafted; decision block left for the manager."46```47## Output format48`CASE-<case_id>.md` following the template's numbered sections 0-9. In chat: routing line, determination + clause, recommendation, signal count, and the two drafts' status.49## Grounding requirements50Every claim cites order, receipt, history, clause or config. Customer-facing text states only what policy text and the record support - no processing times, refund timings or goodwill promises unless quoted from policy text (#5.0).51## Guardrails52- Never fabricate facts, timings, approvals or review outcomes; every claim cites the payload, policy text or config.53- Never authorise a refund, release funds, adjudicate fraud, dispose inventory, book a carrier, or send the response to the customer (plugin boundary).54- Signals appear as signals in the internal sections only; the customer response never mentions suspicion, fraud or asset protection.55- Never state that asset protection or a manager has reviewed or cleared anything unless the payload records it.56- Never fill the manager's decision block.57## Escalation / uncertainty58If `governed.json` lacks an `eligibility` block, stop and route the case back through eligibility-check - never decide here. If a template slot has no source, write `not on record`; never fabricate a value to fill it.59hold_for_review packets route to asset protection with the signal citations attached; missing payload fields are written as `not on record` and listed under Missing evidence.