Interactive setup wizard for the plan-my-day skill. Walks users through configuring their repositories, branch naming conventions, Jira project keys, and output preferences, then generates a config.yaml file. Use when the user asks to set up or configure plan-my-day, or says "set up my daily plan" or "configure plan-my-day".
Interactive setup wizard for the plan-my-day skill. This generates a
config.yaml file so the daily planning skill knows which repos, Jira
keys, and branch conventions to use.
Read ~/.claude/skills/plan-my-day/config.yaml.
Ask the user: "What repos do you work in? Give me their local paths."
(e.g. ~/projects/my-app, ~/projects/my-api)
For each repo path provided:
ls <path>/.git
git -C <path> remote -v
origin fetch URL to extract the org/repo value. Show it to
the user for confirmation.git -C <path> branch --sort=-committerdate --format='%(refname:short)' | head -20
prefix/key-NNN pattern (e.g. jsmith/cpd-123),
suggest branch_ticket_format: prefix/key-NNN and extract the prefix.key-NNN pattern (e.g. cpd-123),
suggest branch_ticket_format: key-NNN.my-app).Ask the user:
"What Jira project key(s) do you use?" (e.g. CPD, PROJ)
getAccessibleAtlassianResources to confirm the
Jira MCP connection works. If it fails, warn the user but continue
(they may set up Jira later)."Where should I save the daily plan file?" (default: ~/Desktop/dayplan)
If a branch prefix was detected in Step 2, confirm it: "Your branches seem to use the prefix 'jsmith'. Is that right?"
branch_prefix.For each repo, verify gh CLI access:
gh auth status
If not authenticated, warn the user:
"GitHub CLI isn't authenticated. Run
gh auth loginbefore using/plan-my-day. PR lookups won't work without it."
Assemble the config.yaml from all gathered values:
branch_prefix: <detected or user-provided>
jira_keys:
- <KEY1>
- <KEY2>
output_path: <user-provided or ~/Desktop/dayplan>