Agile Frontier

Agile Frontier turns a backlog into a delivery plan you can act on. Paste or edit JSON stories, set a deadline and team capacity, and it schedules the work while respecting dependencies.

The current module release is v0.2.3.

The planner calculates each story’s earliest start, latest safe start, slack, and critical-path membership. Work is colored red, yellow, or green by urgency, making it clear which unblocked stories can be picked up as soon as current work finishes.

Story format

Each story uses the requested portable shape:

{
  "title": "Publish the vanity module",
  "links": ["Build the planner"],
  "points": 3,
  "status": "todo"
}

links names prerequisite stories. Completed and canceled work does not consume future capacity. The interface also supports assignee, team, and sprint fields, with sensible defaults when they are omitted.

Planning model

• Dependencies form the delivery graph and expose cycles as input errors.
• Story points become duration using the configured points-per-day rate.
• Worker capacity produces a realistic resource-constrained schedule.
• Backward scheduling from the deadline gives every story a latest safe start.
• Critical-path stories are highlighted, while frontier depth helps select the next useful unblocked work.

Go+ and WebAssembly

The planning engine is authored in Go+, using its concise collection and data transformation abstractions, then compiled to Go and WebAssembly. Scheduling runs locally in the browser: backlog data does not need to leave the machine. The generated Go package remains consumable through the normal Go module ecosystem at goforge.dev/agilefrontier.

License

MIT. Source and release history are in the repository.