Journey Plan

Takes your idea document and turns it into a concrete Butterbase architecture: tables with columns and types, RLS policies, auth providers, function triggers, storage buckets, and frontend stack choice. Works interactively, asking one question at a time instead of dumping a form on you. The scope-cutting logic is smart in hackathon mode, forcing you to split features into "ship now" versus "post-hackathon" so you actually finish. Also checks if you need Composio integrations or Stripe before you reinvent payment flows. If you're publishing as a template, it plans the README and env-var setup too. Outputs a structured plan that the downstream build skills can execute against without ambiguity.

GitHub stars: 532
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add butterbase-ai/butterbase-skills --skill journey-plan --agent claude-code

Installs into .claude/skills of the current project.

Files

Journey: Plan

Stage 2 of the guided journey. Turn the idea brief into an actionable Butterbase plan.

When to use

Dispatched by journey when current_stage: plan.
Directly via /butterbase-skills:plan.

Inputs

docs/butterbase/01-idea.md (must exist — if absent, bounce back to journey-idea).
docs/butterbase/00-state.md (for hackathon_mode, hackathon_deadline).

External services — check built-ins first

When the plan needs email, messaging, calendar, CRM, docs, or project-management integration:

Invoke butterbase-skills:integrations and call manage_integrations action: "list_available" to see what Composio covers for this app.
If a toolkit fits, the plan should record "via manage_integrations (toolkit: )" instead of naming an external SDK.

When the plan needs payments:

Invoke butterbase-skills:payments.
Default to Stripe Connect via manage_billing unless the user's region forces a fallback (see the payments skill).
Record the choice ("Stripe Connect" or " via function proxy") in the plan's Payments section.