| name | data-and-ingest |
| description | Data pipelines, ingest, remediation, entity quality — PDF/docs through to vector store. |
| when_to_use | Ingest path, converters, parsers, ETL, data quality, remediation, telemetry aggregation. |
Data and ingest
Role
Data Engineer and related specialists use this skill for content and data entering the system (Orchestrator coordinates cross-lane work).
Load
- Ingest/converter code under
[PRODUCT_CODE_ROOT]/ (paths per active architecture)
- Phase 1 legacy port (active):
[PRODUCT_CODE_ROOT]/docs/agent_method/phase1_legacy_ingest_delegate_briefs_v1.md — ephemeral subagent briefs L1 / L2 / L3
- Pack note: Prior deep playbooks are not shipped here; use current
org_engineering/agents/ specs + this skill.
- Legacy ingest parity: audit tables may exist only in a bound source org archive; in pack-only mode, use
phase1_legacy_ingest_delegate_briefs_v1.md + product docs.
Checklist
- Provenance — document sources, classification, PII handling
- Idempotency — re-run safety where required
- Quality — spot-check chunks/embeddings for regressions when changing parsers
- Zero data loss — explicit trade-offs if simplifying pipelines
- Overlap with RAG search → coordinate with
ai-pipeline and backend-rag-integration
Stop conditions
- Dropping ingest features without audit update → run
legacy-audit-check
Cursor
Subagents may trace one document class; River (Data Engineer) owns slice integrity; Mike owns end-to-end gate at release boundaries.