Fatih Arslan's markdown-plan workflow for running a fleet of coding agents

Cursor's Fatih Arslan details a git repo of markdown plans, moved through drafts/next/open/done by skills and run by Cursor Projects coordinators.

Fatih Arslan, who works at Cursor, has published how he manages a fleet of coding agents (September 11, 2026). The pattern is copyable: every piece of agent work is a single markdown plan in a dedicated git repo. Plans move through drafts/, next/, open/, done/ and discarded/ folders, driven by skills such as /plan-add, /plan-write, /plan-dispatch and /plan-sync. Git gives him shared access for agents and co-workers, plus history, at no extra cost.

The core rule is that a plan only reaches next/ once it holds every decision, so a fast coding model can implement it without asking design questions. A plan in next/ is meant to end as one or more PRs. A /plan-retro skill reads finished plans and proposes edits to the skills themselves.

He now runs plans through coordinators from Cursor Projects, which is in beta. Coordinators can't message each other, so they leave dated inbox and handoff files in git. That also let him rebuild a Project from the repo after a platform bug. Cursor has not disclosed pricing for Projects.

This is one person's setup, not a benchmark. Arslan deliberately didn't publish the skills. Instead he gives a prompt that has your agent generate versions tuned to your own history. The post doesn't say how several coordinators avoid conflicting writes to the plans repo, or whether the workflow needs Projects.

If you'd rather install something, planning-with-files keeps markdown plans on disk within a single project. addyosmani/agent-skills packages spec-to-ship skills. Claude Code users have Projects on top of cloud sessions.

Sources