setup
/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.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Triggers from the description
Original author description
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.
How it works
- Asking questions
- Operating mode
- Config file contract
- Phases
- Constraints
SKILL.md preview
---
name: setup
description: 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.
---
# /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.json` and (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 `.gitignore` lines. Only append when missing.
- **Defaults are the historical path.** `plansDir` defaults to `.claude/plans`; `gitignore` defaults to `true`. Users who never run `/setup` get the same behavior as before.
## Config file contract
`.claude/plans-config.json`:
```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. If `true`, skills ensure `plansDir` is in `.gitignore`. If `false`, skills do not touch `.gitignore`.
## Phases
### Phase 1 — Detect existing config
Read `.claude/plans-config.json` if it exists. If present:
1. Show the current values.
2. Ask via `AskUserQuestion`: "Config already exists. Reconfigure or keep as-is?" with options "Keep" (Recommended) and "Reconfigure".
3. If "Keep", end the turn after printing the current config.
4. 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.
1. **Plans directory.** Options: `.claude/plans` (Recommended), `Other` (user types a path). Accept absolute or relative paths.
2. **Gitignore the plans directory?** Options: `Yes` (Recommended), `No`.
### Phase 3 — Write config
1. Create `.claude/` if it does not exist.
2. Write `.claude/plans-config.json` with the chosen `plansDir` and `gitignore` values.
3. If `gitignore: true`:
- If a `.gitignore` exists at the project root and does not already contain a line matching `plansDir` (with optional trailing `/`), append `<plansDir>/` to it.
- If `.gitignore` does not exist, create it with that single line.
4. If `gitignore: false`:
- Do **not** modify `.gitignore`.
- If `.gitignore` exists and already contains a line matching `plansDir`, print a note: "Your `.gitignore` still contains `<plansDir>`. Remove it manually if you want plans tracked in git."
### 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.json` and `.gitignore`.
- Never remove existing `.gitignore` lines.
- Defaults must match the historical behavior (`.claude/plans`, gitignored).
- Ask questions via `AskUserQuestion`; one question at a time; recommended-answer option first.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · vpaivag/skills | 100 | MIT |
| HwangSlater/harness-fit | 100 | MIT |
| nesquikm/dev-process-toolkit | 100 | MIT |
| userKael/rastro | 100 | MIT |
| als-apg/osprey | 100 | BSD-3-Clause |
| dedujeong/gemba | 100 | Apache-2.0 |
| eigenwise/eigenwise-toolshed | 100 | MIT |
| awrshift/agent-memory-kit | 100 | MIT |
| lifecycle-innovations-limited/claude-ops | 100 | MIT |
Database snapshot: 13.11.2026 · package version 01e752cdf64d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100configure-gitignore
Manage .gitignore's Claude Code block — worktrees, scheduled-task lock, local settings. Use when onboarding a repo or .gitignore lacks Claude entries. - 100godot-project-setup
Use when creating a new Godot 4.x project — scaffolds recommended directory structure, project settings, autoloads, and .gitignore - 95project-config
[Utilities] Use when syncing the project-config file (default docs/project-config.json) with the current workspace structure. Not reference docs (scan) or CLAUDE.md (ai-context-refresh). - 95project-config
[Utilities] Use when syncing the project-config file (default docs/project-config.json) with the current workspace structure. Not reference docs (scan) or CLAUDE.md (ai-context-refresh). - 100godot-project-setup
Use when creating a new Godot 4.x project — scaffolds recommended directory structure, project settings, autoloads, and .gitignore - 100init-repo
Bootstrap a new n8n workflow repo from scratch. Scaffolds directory structure, writes plugin-compatible CLAUDE.md/README/.gitignore/.env.example, runs the n8nac >= 2.3 setup flow (`env add` + `env auth set` + `env use`), pulls node schemas, and verifies setup. Use when starting…