Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →butterbase-ai/journey-plan
Use as stage 2 of the Butterbase journey, after journey-idea has written 01-idea.md. Translates the idea + capability map into a concrete Butterbase plan — tables (with columns/types/RLS shape), auth providers, function list (name + trigger), storage buckets, AI/RAG/realtime/durable usage, and the chosen frontend stack. In hackathon mode, ruthlessly cuts scope into a "ship now" vs "post-hackathon" split. Produces docs/butterbase/02-plan.md.
Passed 14 of 19 test cases with the skill, and 7 of 19 without it.
and 14 more in the full report
11 fixed6 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When publish_as_template is set to yes in state front-matter, what key environment variable handling rule must be documented in the template README outline section of the plan?
| Checked | Without skill | With skill |
|---|---|---|
| Distinguishes between auto-minted keys like butterbase_api_key and manual input keys for cloners. | Missed | Passed |
The instructions your model reads when the skill loads.
Stage 2 of the guided journey. Turn the idea brief into an actionable Butterbase plan.
journey when current_stage: plan./butterbase-skills:plan.docs/butterbase/01-idea.md (must exist — if absent, bounce back to journey-idea).docs/butterbase/00-state.md (for hackathon_mode, hackathon_deadline).When the plan needs email, messaging, calendar, CRM, docs, or project-management integration:
butterbase-skills:integrations and call manage_integrations action: "list_available" to see what Composio covers for this app.When the plan needs payments:
butterbase-skills:payments.manage_billing unless the user's region forces a fallback (see the payments skill).Work through these sections in order. After each section, write the result to 02-plan.md before moving on. One question at a time per the spec's questioning discipline.
Tables. Read the capability map. Propose a starter table list with columns and types — recommend, don't ask blank. Example: "Tables I'm seeing: users, orders, items. Missing any?" Then for each table: "<table>.<column>: should this be a uuid / text / int / timestamp / enum?". Confirm primary keys, foreign keys, indexes that are obvious (foreign-key columns).
RLS model. For each table: "Can user A see user B's <table> rows? ① no, strict isolation ② yes, public-read ③ only shared via explicit grant." Decide policy shape. In hackathon mode, prefer option ① and recommend manage_rls action: create_user_isolation.
Auth. "OAuth providers: ① Google only ② Google + GitHub ③ email/password too ④ none (anonymous app)." Also ask: "Need a demo / judge account seeded? (hackathon mode only)".
Functions. For each function from the capability map: "<name>: trigger = HTTP / cron / WebSocket? If cron: schedule? If HTTP: idempotency needed?".
Storage. If used: "Which objects (avatars, attachments, …)? Public-read or per-user?".
test cases passed, vs 7 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.