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.
Profile →npx skills add butterbase-ai/butterbase-skills --skill journey-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: 1. Invoke `butterbase-skills:integrations` and call `manage_integrations` `action: "list_available"` to see what Composio covers for this app. 2. If a toolkit fits, the plan should record "via manage_integrations (toolkit: <name>)" instead of naming an external SDK. When the plan needs payments: 1. Invoke `butterbase-skills:payments`. 2. Default to Stripe Connect via `manage_billing` unless the user's region forces a fallback (see the payments skill). 3. Record the choice ("Stripe Connect" or "<regional gateway> via function proxy") in the plan's Payments section. ## Procedure Work through these sections in order. After each section, write the result to `02-plan
- When to use
- Inputs
- External services — check built-ins first
- Procedure
- Toolchain question
- 02-plan.md format
- Outputs
- Anti-patterns
What does the journey-plan skill do?
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.
How do I install it?
Run `npx skills add butterbase-ai/butterbase-skills --skill journey-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From butterbase-ai/butterbase-skills, a repository with 532 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.