David Morais's multi-agent setup
David Morais · Catalog date October 16, 2026
David Morais plans in Claude Code and implements in Cursor. A Project Planner writes plan.md, an Orchestrator splits the work and assigns agents, Code Pusher opens the pull request, and a Gilfoyle reviewer grades findings by severity. plan.md is the handoff if one provider stops mid-task.
Evidence. Sourced, incomplete
A public source is linked. Some results, prompts, or operating details are still unknown. This catalog has not re-run the crew.
- Goal
- Keep a task moving between Claude Code and Cursor through one file
- Use
- Software
- Platforms
- Claude Code, Cursor
- Crew size
- Multiple agents, count not stated
- Difficulty
- Not stated
Roles
The post calls this a small fleet of custom agents and skills on top of Claude Code and Cursor. It names the four roles below and a Project Agent Creator skill, which scans a project and decides what should be an autonomous agent versus a skill. The Orchestrator assigns "the right agent" to each micro-task. The post does not give a headcount, so unlisted agents are not invented here. Antigravity and OpenCode are described as backups, not as these four roles.
Constraints shared by every role
To be added.
Project Planner
Owns. Holds project and roadmap context, breaks down tasks, and writes plan.md in the repo.
Uses the shared constraints above.
Orchestrator
Owns. After a task list is locked, splits the work into micro-tasks, assigns an agent to each, and updates plan.md while the work is in progress.
Uses the shared constraints above.
Code Pusher
Owns. Stages changes, runs pre-commit checks, writes commit messages in the repo's convention, and opens the pull request. Applies minor review feedback before it reaches the author.
Uses the shared constraints above.
Gilfoyle reviewer
Owns. Reviews pull requests and grades security flaws, performance regressions, and architectural anti-patterns by severity. The post says it is built on gilfoyle-code-review.instructions.md templates.
Uses the shared constraints above.
Routines
Per task
Each task
The planner writes plan.md, the orchestrator keeps that file current as micro-tasks move, and Code Pusher opens the pull request.
Guardrails
- plan.md is the handoff between providers. The post says the author can give the file to another tool, Claude to Cursor, and continue if one provider runs out of tokens or goes down.
- Minor review feedback is applied by Code Pusher before it reaches the author. The post does not say every pull request waits for the author.
Handoffs
plan.md moves the plan between Claude Code and Cursor. The Orchestrator assigns micro-tasks to agents and updates the file. Code Pusher opens the pull request. The Gilfoyle reviewer grades that pull request by severity. The post does not name the other agents the Orchestrator assigns.
- Project Planner
- Orchestrator
- Code Pusher
- Gilfoyle reviewer
Human operator
plan.md moves the plan between Claude Code and Cursor. The Orchestrator assigns micro-tasks to agents and updates the file. Code Pusher opens the pull request. The Gilfoyle reviewer grades that pull request by severity. The post does not name the other agents the Orchestrator assigns.
Results
- What worked
- To be added.
- What broke
- To be added.
- Lessons
- To be added.
Prompts
To be added.
Source
David Morais, June 26, 2026
https://davidmorais.com/en/blog/my-multi-agent-setup
Notes
The catalog date is the day this entry was drafted. The post is dated June 26, 2026.
The post also describes Antigravity for front-end work from a screenshot, and OpenCode for routine updates to memory files such as MEMORY.md. It includes a price snapshot for several tools, current as of June 2026 in the author's words. Those prices are not results of this crew, and they are not copied here. The post does not report what the fleet shipped, what broke, or a prompt. Difficulty is not stated. The earlier research note that the reviewer must sign off on pull requests is not what the post says. Minor feedback is applied before it reaches the author.