According to story card best practices, when can you change a requirement number?

Changing a requirement number is best done before it is published. This is grounded in the understanding that once requirements are shared and documented as part of the project, they are understood by all stakeholders and referenced accordingly. Publishing a requirement solidifies it within the project, making it part of the official documentation that team members will rely on throughout the development lifecycle.

Changing requirement numbers after publication can lead to confusion, miscommunication, and potential errors in tracking and meeting those requirements, as stakeholders might not be aware of the changes. Therefore, adhering to the standard practice of modifying requirement numbers only before publication helps maintain clarity and ensures that everyone involved in the project is on the same page regarding the requirements throughout its execution.