intake-validation
Correlate a return case with its order and customer profile, and validate completeness. USE FOR intake of a new return, matching an RMA to an order, checking required fields/photos. DO NOT USE FOR the eligibility or refund decision (that is policy-eligibility / disposition-decision).
ソース情報
- リポジトリ
- aiappsgbb/threadlight-skills
- ソースの最終更新活動
- 2026年9月8日 13:38
- 検出された SKILL.md の言語
- 英語
- スター
- 1
- フォーク
- 5
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- name
- intake-validation
- description
- Correlate a return case with its order and customer profile, and validate completeness. USE FOR intake of a new return, matching an RMA to an order, checking required fields/photos. DO NOT USE FOR the eligibility or refund decision (that is policy-eligibility / disposition-decision).
# Intake & Validation
> Implements BR-004 (partial: completeness gate) and feeds BR-001/002/003.
## Operational contract
- **Inputs**: an RMA id or an order id.
- **Outputs**: a consolidated case object `{ return, order, customer }` and a
nonterminal `complete` / `incomplete` verdict with the missing items. Intake
never chooses a persisted decision before the known-risk gate.
- **Deps**: tools `returns_get_case`, `oms_get_order`, `customer_get_profile`.
- **Idempotency**: read-only; safe to re-run.
- **Failure behavior**: if any of the three fetches fails after retries → mark the
case `system_error` and hand to fraud-escalation for escalation.
## Procedure
1. Resolve the case: if given an RMA, call `returns_get_case`; if given an order id,
call `returns_list_open` and match.
2. Fetch the originating order via `oms_get_order(return.order_id)`.
- If `not_found` → collect "order could not be matched"; continue the customer read.
3. Fetch the customer via `customer_get_profile(return.customer_id)`.
4. Completeness check (BR-004):
- `reason_code` present?
- if `reason_code == arrived_damaged` → `photos_provided == true`?
- order line matched to the returned SKU?
- Any failure → collect the exact missing field(s), without finalizing a verdict.
5. Pass the consolidated case and missing fields to fraud-escalation. Known
authoritative BR-003 risk requires `escalate_to_supervisor` even on incomplete
cases. Only without known risk choose `request_more_info`; never refund while
risk data is unknown. Complete cases continue to policy-eligibility.
## Output schema
```json
{ "verdict": "complete | incomplete",
"missing": ["reason_code"],
"case": { "return": {}, "order": {}, "customer": {} } }
```
GitHubで見る