Summary
Dependencies stop being something you hold in your head.
The method is the ordinary one - start at the outcome and work backwards - but the payoff is the queries: what can I start now, what is blocked, and which steps actually determine the end date. Those are the three questions a plan written in a document cannot answer.
What it is
A backcasting planner. A plan starts from a desired future state and is broken into steps with dependencies; the tools then answer what can be done now, what is blocked, and which steps sit on the critical path.
What you get
- Plans created, listed, loaded and exported
- Steps added, updated, deleted and listed, with a status tracked on each
- A plan overview, and the full detail of any single step
- The next actions available right now
- The steps currently blocked
- The critical path through the plan
- An analysis pass across the whole plan
Requirements
Python. It runs locally and keeps the plans it creates - no account and no API key.