Skip to main content

Prompts

Store prompts here when they are reusable, owned, testable, and connected to a real workflow. Include required inputs, the expected output, constraints, and at least one example or evaluation method.

Spreadsheet enrichment workflows​

The enrich_o package preserves the source row grain, uses explicit row statuses, stops failed rows at controlled gates, and writes results to a new workbook. Stage 1 reads the full export locally and creates a compact working workbook containing only the minimum source fields required by the downstream stages. The full export is never sent to later model prompts.

Stages and statuses​

Full source workbook (unchanged)
|
v
+--------------------------------------+
| Stage 1: CHECK + COMPACT |
| Reads full file locally |
| Creates compact file and adds status |
+------------------+-------------------+
|
+-----------+-----------+
| |
v v
ready bad_data [STOP]
| error [STOP/retry]
v
+--------------------------------------+
| Stage 2: VALIDATE |
| Resolve one real company |
+------------------+-------------------+
|
+-----------+-----------+
| |
v v
valid invalid [STOP]
| error [STOP/retry]
+----> [STOP when no enrichment applies]
|
v
+--------------------------------------+
| Enrichment 1 |
| Required input: valid |
+------------------+-------------------+
|
+-----------+-----------+
| |
v v
enriched_1 [STOP] error [STOP/retry]

Statuses move forward only. bad_data and invalid are terminal. error is retryable only when the selected orchestrator enables retries. The pipeline stops after enriched_1 and can resume later from the compact working workbook.

enrich_o: lean routing enrichment​

enrich_o separates basic readiness, semantic validation, and enrichment into pure stage prompts. The enrich_o orchestrator is the only workbook writer and enforces legal transitions, field ownership, resumability, and the max_enrich_steps limit. Its Stage 1 output retains 13 compact ZoomInfo identity and routing fields, adds enrichment_status, and becomes the state store for validation and enrichment.

The current registry supports max_enrich_steps: 1. Its first enrichment step owns only:

  • market_motion
  • motion_priority
  • vertical
  • m1_current_scope
  • sub_vertical
  • sub_vertical_candidates
  • segment_priority
  • segment_operating_status
  • proof_transfer_rule
  • vertical_membership
  • classification_status

Sample run prompt​

<grounding>
[enrich_o orchestrator](docs/prompts/enrich_o/orchestrator.md)
</grounding>

<settings>
input_file: sample-data/owner1.xlsx
output_file: sample_data/owner1_enriched_o.xlsx
max_enrich_steps: 1
source_sheet: null
retry_errors: false
resume_existing: true
</settings>

<task>
Run the enrich_o pipeline exactly as specified by the orchestrator. Preserve
all source rows and create the compact Stage 1 working workbook without
modifying the source export. Continue through the configured gates and return
the compact enriched workbook with final counts by enrichment_status.
</task>