diff --git a/CHANGELOG.md b/CHANGELOG.md
index df54ce80ff2a38d6b83205fcc505804bf2fb684b..b605fdac7299d5a7ba7d0fdc548fc984d6cd370a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,6 +1,6 @@
 ## [0.0.89-RELEASE] 
 ### Added
-- New features that have been added.
+- Add README.md
 
 ### Changed
 - Changes in existing functionality.
diff --git a/README.md b/README.md
index 1ae54772b4c163b2fa3929df750a50afab418e88..dc497eb0754ee9da8d7f86d8d841afe8a2512ff9 100644
--- a/README.md
+++ b/README.md
@@ -1,93 +1,46 @@
-# mc-starter
+# MC-Starter
 
+## Project Objective
 
+The `mc-starter` project is a parent project designed to be the foundation for all client projects of Marketing Confort. It provides a generic configuration and reusable modules to facilitate the development and deployment of new client applications. This project also includes scripts and CI/CD pipelines to automate versioning, deployments, and notifications.
 
-## Getting started
+## Important Instructions
 
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+### Code Modification and Addition
 
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+When adding or modifying code in this project, it is essential to follow certain rules to ensure the quality and maintainability of the code:
 
-## Add your files
+1. **Packaging Line**: To start the project locally, you need to modify the packaging line in the `pom.xml` to `jar`. **Do not push this modification**, or your MR will be rejected. Here’s how to do it:
+   - Open the `pom.xml` file and change the following line:
+     ```xml
+     <packaging>pom</packaging>
+     ```
+     to:
+     ```xml
+     <packaging>jar</packaging>
+     ```
 
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+   - Compile and run the project locally.
 
-```
-cd existing_repo
-git remote add origin http://mc-git.com/marketing-confort/mc-starter.git
-git branch -M main
-git push -uf origin main
-```
+   - Once your local changes are tested and validated, revert the packaging line to `pom`:
+     ```xml
+     <packaging>pom</packaging>
+     ```
+2. **Update the Changelog**: Every time you make changes, you must update the `CHANGELOG.md` file with the changes you have made. If the `CHANGELOG.md` file is not updated, your Merge Request (MR) will be rejected. Directly modify the first displayed part, which is generated automatically after each deployment, adding what you did for the version you are working on:
+    ```markdown
+    ## [Version] 
+    ### Added
+    - Description of new features or improvements.
+    ### Changed
+    - Description of changes.
+    ### Removed
+    - Description of removals.
+    ```
 
-## Integrate with your tools
 
-- [ ] [Set up project integrations](http://mc-git.com/marketing-confort/mc-starter/-/settings/integrations)
 
-## Collaborate with your team
+### Notification
 
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+After your MR is merged, you will receive a notification of the released version on the `gitlab-release` channel.
 
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+By following these instructions and adhering to the established rules, you will help maintain the quality and consistency of the `mc-starter` project.
diff --git a/scripts/check_pom.sh b/scripts/check_pom.sh
index 49479c82e4259c9170f6b797e99341bc2be32eac..d40f3e4d1801adf24ee336ebc0df51657672e05c 100644
--- a/scripts/check_pom.sh
+++ b/scripts/check_pom.sh
@@ -7,13 +7,16 @@ apt-get update && apt-get install -y curl jq
 POM_UPDATED=false
 INVALID_CHANGE=false
 
+# Fetch the changed files in the merge request
 FILES=$(curl --header "PRIVATE-TOKEN: $GITLAB_API_TOKEN" "https://mc-git.com/api/v4/projects/$CI_PROJECT_ID/merge_requests/$CI_MERGE_REQUEST_IID/changes" | jq -r '.changes[] | .new_path')
 
 for file in $FILES; do
   if [[ "$file" == "pom.xml" ]]; then
     POM_UPDATED=true
+    # Fetch the content of the pom.xml file in the current commit
     CONTENT=$(curl --header "PRIVATE-TOKEN: $GITLAB_API_TOKEN" "https://mc-git.com/api/v4/projects/$CI_PROJECT_ID/repository/files/pom.xml/raw?ref=$CI_COMMIT_REF_NAME")
-    if echo "$CONTENT" | grep -q "<packaging>pom</packaging>"; then
+    # Check if the content does NOT include the required line
+    if ! echo "$CONTENT" | grep -q "<packaging>pom</packaging>"; then
       INVALID_CHANGE=true
       break
     fi