What problem does it solve? It automates the first stage of a 15-agent Databricks SDLC pipeline by turning a raw Jira ticket (or simulated ticket row) into a structured, contract-validated Requirement Package that downstream agents can consume without manual handoffs. ## Core Features & Use Cases - Jira Ticket Ingestion: Polls the Jira REST API or reads simulated rows from the state.tickets Delta table, extracting descriptions, attachments, comments, and acceptance criteria. - Attachment Parsing & Embedding: OCRs and parses PDF/DOCX/XLSX attachments into text, then chunks and embeds them into the knowledge.requirements_index Vector Search index for downstream retrieval. - Contract-Validated Output: Writes requirement.json and attachments.json to /Volumes/{catalog}/state/artifacts/{ticket}/, validates against a strict JSON output contract, and logs full traces to state.agent_runs. - Use Case: A data platform team receives a new Jira ticket for a pipeline change; this agent fetches it, parses the attached spec documents, and hands a validated Requirement Package to the Requirement Validation Agent automatically. ## Quick Start Ask the agent to process Jira ticket PROJ-123 and write its Requirement Package artifact to the lakehouse for the next pipeline stage.