Most project management tools want to be everything for everyone. They pile on features, dashboards, integrations, and collaboration modes until the tool itself becomes the project you need to manage. Meanwhile, the way we build software is shifting: Small teams where a human steers and AI agents do much of the heavy lifting are becoming the norm. Sequentia PM is built for exactly this setup.

The idea

Sequentia PM is a desktop application that turns an ordinary folder of numbered files into a full project management workspace. There is no database, no cloud sync, no account to create. Your project is a directory. The files inside it: Markdown, CSV, DBML are the single source of truth, readable by any text editor, diffable by Git, and equally accessible to humans and AI agents alike.

The naming convention is dead simple: prefix each file with a two-digit number and a dash, and Sequentia picks it up as a tab. The GUI application itself is managed by this approach as a demonstration: 00-process.md becomes your process definition, 03-backlog.csv your backlog spreadsheet, 08-models.dbml your entity-relationship diagram. Add a file, get a tab. Remove it, lose the tab. No configuration needed.

This plain-text, file-per-concern layout is not just a design preference, in my opinion it is what makes human-AI collaboration practical. An AI agent can read, edit, and commit project files through the same Git workflow a human uses. No API tokens, no integrations, no special access. The project folder is directly in the shared workspace.

There is another minimalism at play here: the first file in the sequence is your process definition, which doubles as instructions for your AI agent on how you want the project managed. And because the structure carries no assumptions about what you are building, it works just as well for a hardware product, a marketing campaign, or an event plan as it does for software. Swap the process file, adjust the backlog columns, and you have a different methodology for a different domain.

Because everything is just files in a repo, context-switching between projects is trivial. Waiting on a vendor, a customer estimate, or feedback? Commit, switch branches, move on. When it is time to pick up again, the entire project state is right where you left it.

Technology under the hood

The stack is deliberately compact:

  • Electron + React 19 + TypeScript for the desktop shell
  • Monaco Editor for Markdown and DBML editing with syntax highlighting
  • react-data-grid + HyperFormula for the CSV spreadsheet editor, complete with formulas, sorting, and multi-cell copy/paste
  • @softwaretechnik/dbml-renderer for live SVG entity-relationship diagrams
  • Zustand for state management in roughly 75 lines
  • chokidar for watching external file changes

The entire application logic clocks in at around 560 lines of code. The architecture is a clean three-layer sandwich: Electron main process handling privileged file I/O, a sandboxed preload bridge exposing exactly 20 IPC methods, and a React renderer that never touches the filesystem directly.

An EditorRouter component maps file extensions to purpose-built editors - .md opens the Markdown editor with a live preview pane, .csv opens the spreadsheet, .dbml opens the diagram editor. Everything else gets a polite notice that no editor is available yet.

Less is more, by design

What makes Sequentia interesting is not what it does, but what it refuses to do. The project’s design principles spell this out explicitly:

  • Air-gapped by default. Zero network calls, zero telemetry, zero CDN fetches. All libraries are bundled at build time. The app works identically on an airplane and behind a corporate firewall.
  • No artifacts left behind. The application creates nothing in your project directory - no .sequentia/ config folder, no lock files, no metadata. It reads and writes only the files you created.
  • Open formats only. Markdown, CSV, and DBML are plain text. Your data stays yours, editable in vim, diffable in Git, greppable from the terminal.
  • Single-window simplicity. One project, one window, one tab bar. No workspaces, no multi-project views, no nesting. The complexity ceiling is deliberately low.

This is a conscious rejection of the feature-accumulation treadmill. Instead of asking “what else can we add?”, Sequentia asks “what can we leave out and still have a useful tool?”

The project folder itself is self-documenting. The 00-process.md file defines the entire methodology: file sequence, tiered immutability levels (frozen charters, baselined backlogs, living task lists), and change management rules. The tool and the process it supports are one and the same.

Built for human-AI teams

Sequentia’s process definition doesn’t just describe the methodology for humans: it explicitly governs AI agents too. The tiered immutability system doubles as a permission model: AI agents can freely update living files like tasks and schedules (Tier 3), must flag proposed changes to baselined backlogs and estimates (Tier 2), and are forbidden from touching frozen process documents and charters (Tier 1) without explicit human approval.

This is a practical answer to a real problem. When an AI agent works on your project, it needs to understand not just the code but the project structure, constraints, and rules. With Sequentia, all of that context lives in the same directory the agent is already working in. Point an agent at the folder, and it has everything it needs - the process, the backlog, the data model, the task list - in formats it can parse without any special tooling.

The result is a lightweight governance layer for human-AI collaboration. The human defines the vision, constraints, and priorities. The AI executes within those boundaries, updates what it is allowed to update, and escalates what it is not. No SaaS platform required - just files, Git, and clear rules.

Why not just VS Code?

Fair question. The files are plain text, so you could open the folder in VS Code and edit everything there. In practice, that means installing a Markdown preview extension, a CSV editor extension, a DBML renderer, hoping they play well together, and accepting whatever UI each one decides to give you. It works, but it is duct tape.

Sequentia gives you a coherent interface out of the box. More importantly, it makes the process sequence visible. The numbered tabs are not just an organizational trick - they represent a dependency chain. A charter comes before a backlog, a backlog comes before estimates, estimates come before a schedule. When a junior PM or developer opens the project, they see this structure immediately and can understand the impact of their changes: touching an early file cascades through everything downstream.

This matters because Sequentia is not just a tool for experienced project managers. It is a learning environment. Junior developers and PMs can use it to understand how structured project management actually works - how a charter constrains a backlog, how a backlog drives estimates, how estimates feed a schedule. The numbered sequence teaches the discipline by making it tangible.

And frankly, that is where this tool finds its sharpest edge. The industry conversation right now is that entire groups of junior developers are becoming replaceable by AI. Sequentia offers an alternative path: instead of competing with AI at writing code, learn to manage projects and direct AI agents. The tool is designed to make that transition accessible - a junior who understands project structure and can steer AI agents effectively is far more valuable than one who only writes code that an LLM can produce faster.

Who is this for?

Sequentia fits small human-AI teams - a developer or two steering the direction, with AI agents handling implementation, research, and routine updates. If you already live in Git and work with coding agents like Claude Code, Cursor, or Copilot, Sequentia gives your project the structure these agents need to be effective contributors rather than isolated tools. It is project management that both you and your AI can read, write, and commit to.

It ships as AppImage, deb, and Flatpak on Linux, with NSIS installer and portable builds for Windows. The project is GPL-3.0 licensed, an early version, but the core feature set is already usable.

Check it out on GitHub.