veda-setup

name	veda-setup
model	claude-sonnet-4-6
description	VEDA configuration menu. Discovery hub for setting up workflows, registering Slack channels, configuring style guide, archiving projects, and surfacing what else VEDA can do. Use when the user says /setup, "configure VEDA", "what can VEDA do", "set up X", "show me the menu".

Setup Menu

Show the user a numbered menu of configurable VEDA workflows. Route to whichever they pick. Repeatable — run anytime.

Step 1: Read Current State

Read CLAUDE.md, MEMORY.md, and focus/CURRENT.md. Check whether the following are configured:

test -f style/style-guide.md && echo "style:configured" || echo "style:missing"
test -f rhythms/RECURRING.md && echo "rhythms:configured" || echo "rhythms:missing"
grep -c "^| " slack/channel-summaries/_registry.md  # tracked channel count
ls projects/*.md 2>/dev/null | wc -l                # active project count

Use this state to mark menu items as (set up) or (not set up yet).

Step 2: Show Menu

"What would you like to set up? Pick a number, name, or just describe what you need.

1. Re-run onboarding — re-do the first-time interview (use if your situation has changed)
2. Teach me your voice (set up | not set up yet) — so I sound like you when drafting on your behalf — /style
3. Register Slack channels — channels I should watch in morning briefings — (N tracked)
4. Set up recurring rhythms (set up | not set up yet) — gym, family calls, recurring obligations — rhythms/RECURRING.md
5. Create a project — index card or full hands-on workspace
6. Archive a project — move a finished project to projects/_archive/
7. Update focus areas — what's primary right now → focus/CURRENT.md
8. Brainstorm gaps — guided questions to surface what would help most — /brainstorm
9. Configure API integrations — Google Calendar, Gmail, Slack, GitHub

Or tell me what you actually need and I'll figure it out."

Step 3: Route

Map the user's pick to the matching skill or inline workflow:

Pick	Action
1	Re-run .claude/skills/onboard/SKILL.md (skip Step 1 detection — they invoked it)
2	Run .claude/skills/style/SKILL.md
3	Open slack/channel-summaries/_registry.md, ask for channel name + reason + priority, append a row, confirm
4	If rhythms/RECURRING.md does not exist, copy rhythms/_template.md to rhythms/RECURRING.md and interview the user about their weekly/monthly/annual recurring events. If it exists, open it and ask what to add.
5	Inline: ask if it's a light index-card project (projects/{slug}.md) or hands-on directory project (projects/{slug}/ with local CLAUDE.md and BRIEF.md). Then create from the appropriate template.
6	Run .claude/skills/archive/SKILL.md
7	Open focus/CURRENT.md, show current state, ask what changed, rewrite. Archive prior version to focus/archive/YYYY-QN.md first.
8	Run .claude/skills/brainstorm/SKILL.md
9	Open CLAUDE.md, walk through the Available API Integrations table, remove rows the user is not using, add any missing ones. Note that connecting the integrations themselves happens in Claude Code settings, not here.

Step 4: Loop or Exit

After completing one item:

"Want to set up anything else, or are you good?"

If done:

"Run /setup anytime."