Plan work with Planner
Keep goals, tasks, questions, constraints, decisions, and useful memory attached to the app as it evolves.
On this page
Planner shows structured context that Ahamo records while planning and building an app. It starts empty and usually fills over several rounds; you do not need to create paperwork before the first build.
Read the record types
- Goals describe a larger outcome that may need several rounds.
- Tasks are specific pieces of work, with status and a complexity marker.
- Open questions need an answer from you before later work can rely on the choice.
- Constraints are hard or soft rules that Ahamo should preserve.
- Decisions show what was chosen and why.
Planner is a view of what has been recorded, not proof that a feature works. Confirm completed behavior in Build.
Maintain only what helps the next round
Open Planner after a planning or build round and scan for three things:
- Answer an Open question using its field and Answer button.
- Mark a task Done only after its visible result works, or choose Skip when the task is no longer needed.
- Check that active constraints and recent decisions still match what you intend to build.
Goals can be edited or deleted in Planner. Tasks expose Done and Skip, and questions expose Answer. Constraints and decisions are displayed for context; the current pane does not provide a general control for creating or revising every record type.
Use Chat when something new must be recorded. For example:
Record a hard constraint that the public catalog stays available without sign-in. Add a task to verify the signed-in saved-items page on mobile.
A small maintenance workflow
Suppose a product catalog has a goal to let visitors save favorites, a hard constraint that browsing stays public, and an open question about whether saving requires sign-in.
Answer the question, use Plan to agree on the access behavior, then build the change. Test signed-out browsing and signed-in saving in Build. Only then mark the related task Done. If you abandon the feature, choose Skip instead of leaving a misleading active task.
Keep entries specific enough to act on. “Show an empty state when no favorites are saved” is a useful task; “improve favorites” is not. When a decision changes, tell Ahamo which earlier choice it replaces so Planner does not present two competing directions.
Next: Choose Plan or Build mode and review history and undo a build.