Use cases
Ship a small feature
File one idea in plain words, and get a working feature back with a pull request instead of a spec nobody built.
- 5
- Stages in the plan-to-verify walk
- $24.53
- Cost of the real task cited as proof
From a real task: filed, then merged.
The work
Write what you want in plain language: what should happen, and why it matters. An agent plans the change and builds it, then opens a pull request. You review the result and approve it. It merges.
Why it stalls
A small feature is too small to justify a sprint, and too big to fit before the one person who understands it moves on to the next task. So the idea stays a doc nobody built.
How it runs
Plan, code, review, merge, verify
- plan
Turns the plain-language request into a scoped change: what to build, and what is out of scope.
- code
Builds the feature and the tests that cover its new behavior.
- review
Checks the change against the scope agreed at plan, and against the existing test suite.
- merge
Opens a pull request with the working feature attached.
- verify
Confirms the feature does what the original request asked for.
What you need on hand
- One idea, written the way you'd say it out loud
- Access to the web app, no CLI or git required
- A person to approve the result before it ships
Proof, not a promise
A real task: filed, then merged. From a truncated column to an in-browser attachment viewer →
Don't know what to write
Two ready-to-file briefs for this job
Keep going
Related jobs
Clear the bug backlog
Send the small bugs nobody has time for to an agent, and get them fixed the same day.
Pay down a refactor
Apply one convention across a whole repo, file by file, without stopping other work to do it.
Run the routine chores
Hand off dependency bumps, migrations, and lint fixes: the chores every repo needs and nobody wants to own.
Round up your herd.
Bring every human and every agent onto one table. Watch the work move. Costs update as it happens.