Flow template · Development

Planned feature

A spec you approve, two builders in their own copies opening pull requests, and QA that tests both before you merge.

4 chats2 cardsYou decide onceWorks on a repositoryAny AI Morphy connects

Download dev-medium.flow.json Use it in Morphy

Shared by MrApers · 25 October 2026

Left to right, as Morphy lays it out on your canvas: the Start, then each step.

What it does

For a feature that wants a plan. A planner reads your repository and writes a short spec split into one or two tasks; you edit and approve it in a review card. Two builders each take a task in their own copy of the repository (git worktrees on their own branches) and open a pull request each. QA waits for both, checks each pull request out, runs the tests, tries the change and leaves its result on GitHub. The pull requests land in a results card for you to merge. Needs git and GitHub CLI (gh), signed in.

Its brief, which every chat in it works to: Changes go through a branch and a pull request, and the user merges. Never push to the main branch, force-push or delete branches.

Each step

Plannerin the repository: Read the request and the repository, then write a short spec: what changes and why, the files it touches, how it will be tested, and what is out of scope. End with the work split into at most two independent tasks, each under its own heading: `## Task 1` and `## Task 2` (one task is fine for a small change).
Approve the spec: A review card: you read and edit what reaches it, then send it on.
Builder 1in its own copy of the repository: You get an approved spec. Do only its `## Task 1`, in your own copy of the repository on your own branch: make it, run the tests, commit, `git push -u origin HEAD`, then `gh pr create --fill`. Answer with the pull request’s link and what it does.
Builder 2in its own copy of the repository: You get an approved spec. Do only its `## Task 2`, in your own copy of the repository on your own branch: make it, run the tests, commit, `git push -u origin HEAD`, then `gh pr create --fill`. Answer with the pull request’s link and what it does. If the spec has no `## Task 2`, answer only: No second task.
QAin its own copy of the repository: You get the builders’ answers. For each pull request: `gh pr checkout <link>` in your copy, run the tests and try the change the way a user would. Leave the result on GitHub (`gh pr review <link> --comment -b "…"`). Answer with each link and PASS, or what failed and how to see it.
Pull requests: A results card: everything that reaches it, in a list you can mark.

How the work moves

Start hands what you type to Planner.
Planner's answer waits in Approve the spec (a review card) until you send it on.
What you send from Approve the spec goes to Builder 1 and Builder 2.
QA waits until Builder 1 and Builder 2 have both answered, then gets their answers together.
QA's answer lands in Pull requests (a results card).

What you need

A git repository on your computer, with at least one commit
Git, and GitHub’s command line (gh), signed in with gh auth login
Any AI Morphy connects: Claude Code, Codex and the rest

Every change goes through a branch and a pull request, and you merge. Morphy gives each chat that changes code its own copy of your repository, next to it (a git worktree on a branch of its own).

Use it

In Morphy: Settings → Community → Playground → Flow templates, pick Planned feature and click Use this flow. Morphy asks which repository it works on, then builds it.
Or from the file: download dev-medium.flow.json and, on the same page, click Import a file…. It's yours to change, too.
Start it: click Start on the flow and say what it should do.

More development templates

Every flow template

Download Morphy Share a flow of your own