Summary
Requiring a goal to open a session is the one structural decision here, and it is the right one.
A todo list without a stated objective drifts — items get added because they occurred to someone, and nothing tests whether they serve the thing being built. Making the goal the first argument means the plan has something to be checked against. Everything else is deliberately minimal: six tools, no projects, no assignees, no dates. That is either exactly enough for planning a piece of work in a session, or too little to manage anything ongoing, and which one depends entirely on whether you wanted a planner or a tracker.
What it is
A lightweight implementation-planning server: sessions are opened with a goal, todos accumulate against the current plan, and status is tracked per item.
What you get
- start_planning opens a session with a stated goal, so the todos that follow are attached to an intent rather than floating.
- Todos added and removed against the current plan, with completion status updated per item.
- save_plan persists the current implementation plan, and get_todos reads back everything in it.
Requirements
Nothing to supply.
Setup effort
One command — npx -y software-planning-tool