Setup
Configure where plan suites live and whether the plans directory is gitignored. Writes `.claude/plans-config.json` with `plansDir` (default `.claude/plans`) and `gitignore` (default `true`) keys. The planning skills (`/blueprint`, `/build`, `/qa`) read this config to resolve the plans directory, falling back to `.claude/plans` when the config is absent. Use when the user invokes `/setup`, asks to "configure the plans directory", "change where plans live", "set up the plans skill config", or wants to opt in/out of gitignoring the plans directory.From its SKILL.md
npx -y skills add vpaivag/skills --skill setupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.2 KB, as published. Nobody here has run it
/setup
Write a small JSON config that the planning skills consult to find the plans directory and decide whether to manage .gitignore. This skill writes at most two files: .claude/plans-config.json and (optionally) .gitignore.
Asking questions
This skill prefers the AskUserQuestion tool for interactive prompts. If AskUserQuestion is not available (older Claude Code versions, restricted environments), fall back to plain text: print the question, list the options as a numbered list with the recommended option marked (Recommended), and wait for the user's reply (a number or the option label). The skill proceeds normally in either mode — every call site below that says "call AskUserQuestion" follows this fallback rule.
Operating mode
- Two writes max.
.claude/plans-config.jsonand (only if needed) an append to.gitignore. No other writes. - Read-only on code. This skill does not touch any source file.
- Non-destructive on
.gitignore. Never remove or rewrite existing.gitignorelines. Only append when missing. - Defaults are the historical path.
plansDirdefaults to.claude/plans;gitignoredefaults totrue. Users who never run/setupget the same behavior as before.
Config file contract
.claude/plans-config.json:
{
"plansDir": ".claude/plans",
"gitignore": true
}
plansDir: string, relative or absolute path. Default.claude/plans. Relative paths resolve against the project root (the repository), never the user's home~/.claude/. Absolute paths are allowed (some users keep plans outside the repo).gitignore: boolean. Iftrue, skills ensureplansDiris in.gitignore. Iffalse, skills do not touch.gitignore.
Phases
Phase 1 — Detect existing config
Read .claude/plans-config.json if it exists. If present:
- Show the current values.
- Ask via
AskUserQuestion: "Config already exists. Reconfigure or keep as-is?" with options "Keep" (Recommended) and "Reconfigure". - If "Keep", end the turn after printing the current config.
- If "Reconfigure", proceed to Phase 2.
If .claude/plans-config.json does not exist, proceed to Phase 2.
Phase 2 — Q&A
Ask two questions via AskUserQuestion, one at a time, recommended-answer option first.
- Plans directory. Options:
.claude/plans(Recommended),Other(user types a path). Accept absolute or relative paths. - Gitignore the plans directory? Options:
Yes(Recommended),No.
Phase 3 — Write config
- Create
.claude/if it does not exist. - Write
.claude/plans-config.jsonwith the chosenplansDirandgitignorevalues. - If
gitignore: true:- If a
.gitignoreexists at the project root and does not already contain a line matchingplansDir(with optional trailing/), append<plansDir>/to it. - If
.gitignoredoes not exist, create it with that single line.
- If a
- If
gitignore: false:- Do not modify
.gitignore. - If
.gitignoreexists and already contains a line matchingplansDir, print a note: "Your.gitignorestill contains<plansDir>. Remove it manually if you want plans tracked in git."
- Do not modify
Phase 4 — Confirm
Print a summary:
✅ Config written: .claude/plans-config.json
plansDir: <value>
gitignore: <true|false>
<gitignore note if applicable>
End the turn.
Constraints
- Never write outside
.claude/plans-config.jsonand.gitignore. - Never remove existing
.gitignorelines. - Defaults must match the historical behavior (
.claude/plans, gitignored). - Ask questions via
AskUserQuestion; one question at a time; recommended-answer option first.