For teams, typically not everyone uses the same IDE or coding tools ("developer solution"). Using Git hooks, it should be possible to convert between the different formats or layouts (Cursor vs. Claude code, for example) conveniently and automatically.
Plan:
- Evaluate if there exists a common standard (search the web) that works for all solutions.
- If not, suggest a common standard (the issuflow format)
- Make sure that the codebase is refactored so that it can easily switch between solutions
- Create a function and/or a CLI option for converting between solutions.
- create a method that helps users to add git hooks - triggered during pulling (convert to the developers' format)
- triggered during push (or commit?) (Convert to the format decided by the team (where the
issueflow format is one of the options)).
For teams, typically not everyone uses the same IDE or coding tools ("developer solution"). Using Git hooks, it should be possible to convert between the different formats or layouts (Cursor vs. Claude code, for example) conveniently and automatically.
Plan:
issueflowformat is one of the options)).