Recommended workflow
This is the best way to use AIDEN if you want it to feel coherent instead of chaotic.
The short version
- Capture work.
- Shape it into stories.
- Plan the story into a spec.
- Execute in the story workspace.
- Review against the spec.
- Ship and update the board.
That is the core loop.
Phase 1 — Capture work
Put ideas, bugs, and improvements inside the project instead of trying to solve everything in one improvised conversation.
The goal is to turn raw work into visible work.
Phase 2 — Shape the work
Decide whether the idea should become:
- one story
- several stories inside an epic
- something postponed
- something dropped
A good story is small enough to finish and meaningful enough to matter.
Phase 3 — Plan before building
This is where AIDEN becomes much more valuable than a generic AI coding loop.
Create a real spec. Clarify scope. Define success. Make review possible later.
Phase 4 — Execute in the story workspace
Use the story workspace to keep implementation close to the spec and to the execution tools.
That usually means working across:
- story chat
- terminal
- browser
- notes
- files
Phase 5 — Use agents with intention
Use custom agents when specialist roles help. Keep coordination overhead lower than the value it creates.
Do not add more agent motion than the work actually needs.
Phase 6 — Review honestly
Compare the result to the spec. Check whether the acceptance criteria are truly met. Only move to done when the story is genuinely complete.
The philosophy in one sentence
AIDEN works best when you move from vague work to clear stories, from clear stories to real specs, and from real specs to focused execution.