Projects
A project is the top-level operating space for one product, app, service, or codebase inside AIDEN.
If you would normally say, “I’m working on the app,” that usually maps to a project.
What lives inside a project
A project can hold:
- the board
- epics and stories
- project context
- chats related to that work
- agents working in that scope
- Git-aware progress tied to the codebase
Projects give AIDEN a place to keep work coherent over time.
When to create a separate project
Create a separate project when the work has its own:
- repo or folder
- product goal
- workflow
- backlog
- decision history
Do not force unrelated work into the same project just because it is convenient. A clean project boundary makes everything downstream easier.
Ways to start a project
AIDEN usually supports three common entry points:
New project
Start fresh when you are creating something from scratch.
From repository
Use this when the code already lives on GitHub and you want AIDEN connected to that workflow.
From folder
Use this when the code already exists locally and you want AIDEN to wrap structure around it.
What makes a healthy project
A healthy project usually has:
- a board that reflects reality
- stories small enough to move
- specs for meaningful work
- active work kept limited
- clear review boundaries
A messy project is usually a sign that stories are too broad or the board is not being used honestly.
Good project habits
- Keep the project focused on one product area.
- Avoid turning the backlog into a dumping ground.
- Review story scope often.
- Let the board reflect the real state of work.