Cursor
Grok Bot
Grok
MuseTitle99/100
Scope a software project
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Use this when someone wants to know what it would take to build a software product, such as an app, website, SaaS, marketplace, internal tool, AI feature or MVP: how long it would take, what it would cost, what team or tech stack it needs, or a build plan or estimate for their idea. Returns a rough plan with effort ranges for each feature, the team, a timeline range, phases, a suggested stack and a budget (the hours priced at $100 to $150 an hour). The ranges reflect how Pulore builds today, with managed services such as Clerk and Stripe where they fit and AI-assisted development. The plan is calculated locally from fixed estimation tables; this tool does not save a project or call an external service. Map the idea to the closest features in the list and say in your reply what doesn't fit. Results are planning ranges, not a quote. Don't use it for projects that aren't software (like renovations, events or business plans), for task or project management, or to write code.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
project_summary
One short sentence on what they want to build, used as the plan's title. Product details only. Never include payment details, ID numbers, passwords, keys or health records.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
platforms
Where it runs: web, mobile (iOS and Android) or web_and_mobile.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
features
The features it needs. Choose from: accounts (Sign-up, login and user accounts), teams_roles (Teams, roles and permissions), payments (Payments and subscriptions), marketplace (Two-sided marketplace with payouts), admin_panel (Admin panel for your team), dashboards (Analytics dashboards and reports), messaging (Real-time chat or messaging), notifications (Email, push and in-app notifications), search (Search and filters), media_uploads (File, photo and video uploads), maps (Maps and location), booking (Scheduling and bookings), ecommerce (Product catalog, cart and checkout), headless_shopify (Headless Shopify storefront), cms (Content your team edits in a CMS), ai_assistant (AI assistant or chat over your own data), ai_documents (AI document processing (reading, extracting, summarizing)), ai_voice (AI voice agent), integrations (Integrations with a few third-party APIs), offline (Offline mode and sync), multi_tenant (Separate accounts for business customers (multi-tenant)), background_jobs (Data pipelines and background jobs), public_api (A public API for your customers), three_d (3D or AR experiences). For example, subscriptions are payments, a chatbot over their docs is ai_assistant, and a dashboard for their own staff is admin_panel.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
needs_design
True if they don't have designs yet and need design work. If they haven't said, assume true and mention the assumption.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
compliance
Compliance it must meet, if any: hipaa (HIPAA (US health data)), soc2 (SOC 2 readiness), gdpr (GDPR).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations100/100
All four behavior hints are declared.
{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared