36 lines
2.0 KiB
Markdown
36 lines
2.0 KiB
Markdown
---
|
|
name: erp-pdf-delivery
|
|
description: Use when an already exported ERP source artifact must be converted to PDF or handed off, without changing or re-saving the ERP order.
|
|
---
|
|
|
|
# ERP PDF Delivery
|
|
|
|
## Scope
|
|
|
|
This Skill is a separate delivery step after source export. It receives an existing source artifact, prepares a PDF when explicitly requested, verifies the output, and reports a handoff result. It does not create or update an ERP order and is never automatically triggered by create or update.
|
|
|
|
## Workflow
|
|
|
|
1. Confirm that the source export already exists and is associated with an existing ERP identifier.
|
|
2. Preserve the source artifact as the authoritative recovery input.
|
|
3. For an explicit PDF request, use tools/erp_pdf_conversion.js or the approved convert_erp_docs_to_pdf.ps1 workflow with fixture/source files.
|
|
4. Verify that the generated PDF exists, is non-empty, and is readable before delivery.
|
|
5. If conversion fails, keep the source file, report the conversion failure, and offer the source artifact or operator handoff. Do not re-run ERP save, create a duplicate order, or overwrite the source.
|
|
|
|
## Boundaries
|
|
|
|
- PDF conversion is separate from source export and separate from ERP creation/update.
|
|
- Create and update Skills must not trigger this Skill automatically.
|
|
- Never re-save or resubmit an ERP order because a PDF conversion or delivery failed.
|
|
- Do not expose internal workspace paths, browser details, credentials, or traveler PII in a customer-facing message.
|
|
- Use a controlled output directory and retain the source-to-PDF relationship in the handoff record.
|
|
|
|
## Result mapping
|
|
|
|
- source_ready: source artifact is available; PDF was not requested.
|
|
- pdf_completed: PDF exists and was verified.
|
|
- pdf_blocked: source missing, conversion failed, or verification failed; source remains available when present.
|
|
- handoff_required: an operator must deliver or review the artifact.
|
|
|
|
The customer-facing response names the existing identifier, artifact type, and delivery status without exposing internal paths.
|