> For the complete documentation index, see [llms.txt](https://pmse.gitbook.io/pmse-dhdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pmse.gitbook.io/pmse-dhdk/3.-development-plan/3.4-tools-and-workflows.md).

# 3.4 Tools and Workflows

The development of the GNA chatbot is supported by a robust suite of tools and structured workflows, ensuring efficient collaboration, high-quality output, and timely delivery.

* **Version Control**: <mark style="color:blue;">**Git**</mark> and <mark style="color:blue;">**GitHub**</mark> for code collaboration and version management.
* **Project Management**: <mark style="color:blue;">**Trello**</mark> or <mark style="color:blue;">**Jira**</mark> for task tracking, sprint planning, and milestone management.
* **Communication**: <mark style="color:blue;">**Slack**</mark> for team discussions and updates.
* **Development Tools**:
  * <mark style="color:blue;">**Python**</mark> for implementing backend core functionalities.
  * <mark style="color:blue;">**BeautifulSoup**</mark> and <mark style="color:blue;">**MWParserFromHell**</mark> for knowledge-base creation.
  * <mark style="color:blue;">**LangChain**</mark> for RAG system development.
  * <mark style="color:blue;">**FAISS**</mark> for vector store management.
  * <mark style="color:blue;">**Streamlit**</mark> for UI development.
  * <mark style="color:blue;">**Pytest**</mark> for unit and integration testing.
* **CI/CD Pipeline**: An automated Continuous Integration/Continuous Deployment (CI/CD) pipeline is implemented to streamline testing and deployment. This ensures smooth and consistent releases by detecting issues early and automating repetitive tasks.

### Agile Workflow

The project follows an <mark style="color:blue;">**Agile methodology**</mark>, emphasizing iterative development, collaboration, and adaptability.&#x20;

Key Agile practices include:

* **Daily Standups**: Short, focused meetings where team members discuss progress, identify blockers, and set daily goals.
* **Sprint Reviews**: Conducted at the end of each sprint to evaluate deliverables and gather feedback from stakeholders, ensuring alignment with project objectives.
* **Retrospectives**: Held after each sprint to reflect on outcomes, identify areas for improvement, and refine workflows for subsequent iterations.
* **Backlog Refinement**: The task backlog is regularly reviewed and updated to prioritize activities and align with evolving project needs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://pmse.gitbook.io/pmse-dhdk/3.-development-plan/3.4-tools-and-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.