Prompt:
"I am working on a new Git project, and I need a clear feature map for branch naming conventions. The feature map should outline each development phase, the corresponding tasks, and suggested branch naming conventions for each step.
Here are the requirements:
Provide a list of development phases (initial setup, core logic, testing, continuous integration, additional features, linting/formatting, documentation, code review, release, and post-release maintenance). For each phase, describe the objective and the key tasks that need to be completed. For each phase, suggest a branch naming convention following this structure: feat/feature-description, fix/bug-description, release/version, etc. Ensure each phase follows this format: Phase Name Objective: A short explanation of the goal for this phase. Tasks: A detailed list of the specific steps required for the phase. Branch Name: Suggested branch naming convention for the phase. Ensure the format and structure are consistent across all phases. The final output should be formatted as a detailed feature development roadmap for my Git project. Additionally, please include naming conventions for feature branches, bug fixes, hotfixes, releases, and maintenance branches."