Get started
Submit a PRD.
Get back a product.
The agency engages through a product requirements document. Write what you're building and why. The debate begins. Your job is to be available if the agency gets blocked. Everything else is ours.
Setup
Install the plugin
Add Great Minds to Claude Code. One command.
claude plugins install great-mindsOpen a new project
Start a session in your project directory. The agency initializes from BOOTSTRAP.md and enters idle state.
Drop in a PRD
Write your product requirements document — what you're building, who it's for, what success looks like. Save it to prds/ and tell the agency to begin.
Watch it work
Steve and Elon debate. Marcus mediates. Sub-agents build. You can follow the debate in rounds/ and monitor STATUS.md in real time.
Or configure manually
Add to your Claude Code settings:
{
"plugins": ["great-minds"]
}See the full reference at github.com/sethshoultes/great-minds
The PRD Process
What happens when you submit.
Your PRD enters the five-phase pipeline. The agency doesn't build until the strategy is locked. This is what you can expect:
Debate. Steve and Elon read your PRD independently, form positions across all deliverable areas, then challenge each other. No consensus — just the best arguments.
Plan. Marcus mediates conflicts. Decisions lock. Sub-agent teams get assigned with clear mandates and quality gates.
Build. Sub-agents execute in parallel. Design, engineering, copy, brand — all shipping to deliverables/drafts/. You watch in real time.
Review. Steve audits for taste and craft. Elon audits for feasibility and accuracy. Revisions go back with specific feedback — not vague notes.
Ship. Production deployed. Learnings logged to memory. The agency compounds. You get all six deliverables in final/ ready to use.
Writing a PRD
What a good PRD includes.
The agency debates your PRD before reading anything else. Vague PRDs produce vague products. Specific PRDs produce specific, well-argued decisions. Here is what to cover:
What you're building and for whom
What problem it solves that existing solutions don't
Who the primary user is — describe them concretely
What success looks like at 30, 90, and 365 days
What you already know — constraints, existing tech, must-haves
What you don't know — open questions you want the agency to resolve
See prds/ in the repo for the LocalGenius PRD as a reference.
Deliverables
What every engagement produces.
Product Design Vision
Clear product direction informed by first-principles thinking and systems design. Not a wireframe — a statement of what the product is and why it works.
Brand Guide & Identity
Visual language, color system, typography, voice and tone. Consistent across every surface — app, marketing, documentation.
Customer Personas
Real personas with jobs-to-be-done, not demographic summaries. Built from the debate, not from focus groups.
Marketing Messaging
Full messaging framework. Homepage copy, positioning, email sequences, ad briefs. The story that sells the product.
Engineering Specification
Architecture, API design, database schema, deployment topology. A spec an engineer can execute without a meeting.
Built, Deployed Product
The thing itself. Production deployed. Tests passing. CI/CD configured. Not a prototype — a product.
Proof of work
LocalGenius shipped in one session.
736 tests. 166 source files. Two live products. A hybrid AI architecture across five models and two clouds. AI cost at 1.2% of revenue. This is what the agency ships when given a clear PRD.
Ready to begin?
Install the plugin. Write your PRD. The agency takes it from there.
Questions? Open an issue on GitHub.
claude plugins install great-minds