← Portfolio

system-flow

Agentic lean project management that lives inside your repository: a CLI and MCP server for agents, and a kanban dashboard for people

Active – present
  • Go
  • MCP
  • SvelteKit
  • Svelte
  • Tailwind
  • Mermaid
Source →

System-flow is a lean project management system that lives in the repository it manages. Design documents, decisions, and work items (epics, stories, and tasks) are markdown files with front matter, committed alongside the code. People and AI agents work from the same board, and the history of the work is the git history.

flai

flai is the CLI. It creates repositories that follow the standard, and creates, moves, and checks work items, architecture decisions, and agent narratives. It also runs an a host process and MCP server, so agents can pull the next ready story, report progress, and open threads to ask the designer a question. When a story becomes ready, the host can start an agent to work it.

flaiover

flaiover is the dashboard: a kanban board, flow charts, and a searchable explorer for documentation and decisions, across every project on the host. It changes nothing by itself. Every move made on the board is asked of flai on the host, which makes it with your own git identity.

Goals

  • Files are the database. Everything is markdown in the repository, readable without the tools.
  • Pull, don’t push. Work is pulled from an ordered board with work-in-progress limits, by people and agents alike.
  • Resumable. Each story keeps a narrative with its current state and next steps, so any agent can pick up where the last one stopped.
  • One place to see it all. The dashboard switches between projects and shows what needs you.

Features

  • Self-Updating: Dashboard and CLI make upgrades simple
  • Context mapping: flai determines which ADRs and context documents are relevant to the work to optimize agent context
  • Configurable agents: you can configure which harness and model is used by default for your system and customize it per story where needed
  • Agent orchestration: flai monitors for stories you move into ready and determines which stories can be worked in parallel to optimize for throughput
  • Inbox: the dashboard shows when your intervention is required for answering questions or review of completed stories

Context Control Through Documentation

ADRs

Track architecture decisions over time to keep up with how your system’s shape has evolved over time and keep the agents in alignment.

Conventions

Establish your coding conventions via a metadata file and convention files. Conventions are pulled from the either the standard set or your own fork of the standard GitHub repository.

Epics, Stories & Tasks

All work is described via Epics, Stories, and Tasks; markdown files with front matter that helps flai render a visual board and calculate work

Status

In active use: it manages the work on this site, authstar, signet, and several other projects. Install flai with:

curl -fsSL https://raw.githubusercontent.com/bytepunx/system-flow/main/install.sh | sh