Stream exports for large accountsXLAccepted by @jdoe
The format
Every plan is a file
A quest is a Markdown file scoped to one pull request: its objectives, what has been decided, and what stands in the way. Epics are folders, and milestones group them by horizon.
Any agent that can read your repository can find the work. No database, no tracker to sync, and quest check keeps every link and dependency honest.
Your repository
quest/
README.md # The roadmap
m0/
README.md # First milestone, in priority order
export.md # Available
download.md # Requires: export.md
Coordination
Coordinate agents through Git
No server holds the plan. Agents coordinate the way your team already does: with branches and pull requests.
Available
quest unblocked lists the quests with nothing standing in their way.
Accepted by @agent
A live runner lock takes active work. On GitHub, an agent pushes an empty commit to the quest's branch, from a fork too, and opens a draft pull request right away. The earliest open pull request holds the claim.
Ready to turn in
The work lands on that pull request, marked ready for review, plan and code reviewed together.
Quest complete
Merging deletes the plan, Git keeps its history, and the next quest becomes available.
Rendering
As written, as read
The same quest: the Markdown your agents edit, and the page you read.
quest/m0/download.md
# [M] Add a CSV download button
## Goal
People can download their data as a CSV from
the settings page.
## Plan
Call the export endpoint. Show progress, and let
people retry a failed download.
## Required
- [CSV endpoint](/quest/m0/export.md) - the
button needs something to call
## Closes
- [#42](https://github.com/acme/app/issues/42)
Add a CSV download button
M
Requires: CSV endpoint
Objectives
People can download their data as a CSV from the settings page.
Plan
Call the export endpoint. Show progress, and let people retry a failed download.
Requires
CSV endpoint: the button needs something to call
Rewards
Closes #42
Workflow
How it works
Plan with your agent
/quest-plan asks the questions that turn an idea into scoped quests, with dependencies, in priority order.
Run agents in parallel
/quest-start takes one quest to a pull request. /quest-spawn sends several agents out in parallel.
Review and merge
You review every change. /quest-merge lands it once checks and reviews pass, and the next quest becomes available.
In Codex, use $quest-plan and friends. The binary carries the skills, so your repository pins one version.
Roadmap
Long-term plans, as a map
Quest is planned with Quest. Milestones become regions, epics become paths, and every quest is a waypoint coloured by its size. Each deploy charts the tree as it stands.