Git workflow
AIDEN is designed to work with real Git-based software development.
It is not trying to hide Git. It is trying to make AI work cleanly with it.
Why this matters
A lot of AI tooling feels impressive until you need to merge, review, isolate, or trust the result.
AIDEN stays grounded by keeping implementation close to:
- branches
- worktrees
- review stages
- pull requests
- story boundaries
The simple idea
Each story should feel like a real unit of engineering work, not just a prompt history.
That is why AIDEN connects execution to the codebase and to the workflow state.
What this gives you
- cleaner boundaries around active work
- easier review
- less confusion when several tasks are moving at once
- a more trustworthy path from AI output to shipped code
Best practice
Use AIDEN to stay disciplined, not to skip discipline.
If the code changed, the review boundary should still be real. If the story is not complete, do not pretend it is.