How vishwanathbalasubramanian/aiflowcraft-project works
Main Components
• Orchestrator: (src/orchestrator/orchestrator.py) acts as the core controller that manages the LangGraph-based node execution, handling transitions (pause/resume, rejection rerouting) among workflow stages.
• Agents: Located in src/agents, these are modular components for each stage:
• user_input_agent: For generating user stories.
• design_agent: For creating design documents.
• code_agent: For code generation.
• review_agent: For code review.
• qa_agent: For QA assessments.
• Utility Modules: (src/utils) encapsulate the logic for GitHub integration (github_helper), SQLite DB referencing (db_reference), and review logic (review_utils).
• External Integrations: Include external services like:
• GitHub REST API for committing and uploading code post-QA.
• Groq API integration as indicated for API key configuration.
• SQLite for evidence-based generation via a reference database.
• Experimental Modules: (src/experimental) that may be useful for backup/legacy flows or test runs.
Interactions and Data Flow
• UI → Orchestrator: The Streamlit app sends workflow inputs and receives status updates while providing interactive configuration (e.g., review modes, API keys, file uploads).
• Orchestrator → Agents: The orchestrator directs each agent sequentially according to the workflow: starting with user story generation, then design, code generation, review, and finally QA.
• Util Modules: These modules are invoked as dependencies by both the orchestrator and agents (e.g., GitHub helper for uploads, database reference for grounding content, review logic for LLM-based evaluation).
Architectural Patterns & Design Principles
• Modular Design: Each agent and utility is a decoupled component, making testing and extension (e.g., adding a new stage) easier.
• Stateful & Reactive UI: The Streamlit front end maintains session state and continuous log streaming.
• Extensibility and Configurable Pipeline: Emphasize how workflow configurations (different modes, conditional transitions) are managed within the orchestrator.