Aeman

A short-term planning system for engineering teams — keep engineers focused, run daily sprints, and track unplanned work. Built on GitHub Projects v2 (no databa…

LLM Mart 3 views 52 listing impressions

A short-term planning system for engineering teams — it keeps engineers focused, runs daily sprints, and makes unplanned work visible. A git repository is the storage: a board is a repository of small YAML/Markdown files and every action is a commit, so aeman has no database of its own and the board's history is a plain git log. The whole thing ships as one self-contained Go binary: an embedded React SPA (via go:embed), a JSON REST API, a WebSocket watch stream that keeps every open board updated live, and an MCP server for AI agents — all driving the same board service, with the repository as the single source of truth.

Concept

Two complementary views — your own day board and a team board:

  • Me — your own day board. Your cards for the selected day, stacked into four colour zones, with an editable notes log on the right. You can also View as another person to see (and act on) their board, with a one-click reset back to yourself.
    • Gray — regular, planned work.
    • Green — start only when every other zone is clear.
    • Yellow — popped up unplanned during the day.
    • Red — must be resolved before the end of the day.
  • Team — the team board: a people × zones grid for the selected day, filtered by team. Columns are people (with their avatar and name), rows are the same colour zones. Columns can be dragged or shuffled, and a person keeps a column even on days they have no cards.

Each card carries a readiness slider (0–100%), a stage (Locked / Review / Recurrent / Done) that recolours the bar, an optional team, an age counter, and links back to its source issue. Click a card's avatar to reassign its team or person, or the day counter to edit its dates. There is intentionally no built-in time tracker.

Every open board is live: edits made by teammates — or by AI agents over MCP — appear on everyone's screen in about a second, without reloading.

Sprints

Sprints are open-ended and advanced by hand: Carry over starts a team's new sprint on today and pulls its unfinished cards forward (with a no team group too). A card carries two dates — the sprint it belongs to (sprint start) and the day it actually started (start, kept as history) — so the Team board shows it on its sprint's day, on the day it was created, and on past sprint days it passed through. +1 day / +1 week defers a card counting from today, hiding it until its new day without losing that history. The current sprint is tracked per team, so an engineer on several teams sees each team's current cards at once. The full date model lives in docs/dates.md.

Backlog — what is next

Each team has a backlog: one ranked list of the tasks it has accepted and not taken into work, ordered by hand — top is next. A task is either in work (it has a day or a sprint, and stands on the Team and Me boards) or parked in its team's backlog; never both, never neither. The Backlog board shows the selected teams' backlogs as one list, each card with its team and the goal, initiative and epic it sits under; dragging a card reorders it, its team chip hands it to another team, and picking an owner takes it into work — it leaves the backlog and lands on today's boards. The hierarchy (goal ← initiative ← epic ← task, on the Roadmap) says why a task exists; the backlog says when, by position. See docs/design/backlog.md.

Architecture

From the project's README.

Related servers

Universal MCP Server with advanced AI memory capabilities and semantic search.

30 views

MCP server for MikroTik routers: firewall, NAT, routing, DHCP, DNS, WireGuard and more via SSH.

28 views

Let Codex orchestrate external coding agents through their native harnesses.

28 views

Control plane MCP for scoped recon, triage, and bounded proofs.

27 views