How ganeshajdivekar/brd-to-jira works
Project type and purpose
• From the file tree and README, this is a “full-stack AI-powered BRD→JIRA Task Automation” application.
• The provided files are the Next.js 13+ frontend; the README describes a Python/FastAPI backend (OCR, parsing, LLM, task assignment, JIRA sync) which sits behind the UI.
File structure
• Top-level folders:
• app/ (Next.js “App Router” pages and layouts)
• components/ (UI widgets & domain components)
• hooks/ (custom React hooks)
• lib/ (utility functions)
• public/, styles/, config files (Tailwind, PostCSS, Next config)
• The absence of a “backend/” folder confirms the repo is purely the frontend.
• The “components.json” suggests dynamic component registration or a design-system manifest.
README for additional insights
• Confirms multi-stage pipeline:
• Document ingestion (upload UI)
• OCR/Parsing & AI context extraction (backend services)
• Task generation & assignment (backend)
• JIRA sync (when implemented)
• Tech stack: React/Next.js frontend + Python/FastAPI backend + MongoDB/Postgres + LLMs + OCR engine.