> For the complete documentation index, see [llms.txt](https://codethreat-sast.gitbook.io/codethreat-company-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codethreat-sast.gitbook.io/codethreat-company-handbook/handbook/squads/product.md).

# Product

#### Overview

The Product Squad is central to our development, focusing on designing and maintaining our web services' backend and frontend. This team ensures seamless CI/CD processes and flawless product distribution. In our startup environment, we aim to scale methodically, keeping a lean structure and using titles only when essential.

#### Responsibilities

The Product Squad works closely with the founders to identify effective patterns and turn them into user value. These insights shape our sprint planning, built around three-month roadmaps. Each sprint is carefully planned and executed, with details documented in our Product Iteration Playbook.

**AI Integration**

One of the key responsibilities of the Product Squad is the integration of AI-driven features into our products. Utilizing LangChain.js, we develop various AI-assisted functionalities aimed at automating processes and enhancing user experience. These AI integrations are pivotal in maintaining our competitive edge and providing innovative solutions to our users.

#### Technology Stack

{% code title="modules.py" overflow="wrap" fullWidth="false" %}

```
<Distribution>
We deploy using setup bundles and Docker images.

<Development>
Our tech stack includes Deno, ReactJS, TypeScript/JavaScript, MongoDB, REST API, Deno KV, custom build scripts, and Bash scripts.

<Monitoring and Analytics>
We use Amplitude to track user activity and identify issues.

<CI/CD>
We use Azure DevOps for automated and reliable software distribution. All code is stored in GitHub.
```

{% endcode %}

#### Collaboration and Culture

A key part of our culture is the structured interaction between developers and users. We believe that founders or a dedicated technical support team should initially handle user interactions. This allows developers to concentrate on creating high-quality solutions without interruptions.ns.

#### Future Developments

As we continue to grow, the Product Squad will evolve by adding more roles and expanding capabilities. We are committed to transparency and continuous improvement, and will provide future updates and additional details accordingly.


---

# 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://codethreat-sast.gitbook.io/codethreat-company-handbook/handbook/squads/product.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.
