# Setup > Validate the discipline plugin's configuration, the posture-batch overlay and do-your-research-deep's verification depth, and explain how to change it through Claude Code's plugin configuration prompt. Use when: 'set up discipline', 'configure discipline', 'discipline setup', 'is discipline configured', 'what's in my posture batch', 'what's my deep-research depth', or you want to adjust which correctors the batch runs or how deeply the research fan-out verifies. Actions: check (read-only verification, default and only action. This plugin's entire configuration is native userConfig, so there is nothing an apply could write). - Skill: `melodic-software/setup-18` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add melodic-software/setup-18` - Raw SKILL.md: https://api.skillmd.com/api/skills/melodic-software/setup-18/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: melodic-software (https://skillmd.com/u/melodic-software) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/melodic-software/setup-18 --- ## Variables Batch exclude: `${user_config.batch_exclude}` Batch promote: `${user_config.batch_promote}` Batch demote: `${user_config.batch_demote}` Deep-research verification depth: `${user_config.research_deep_verification}` ## Purpose Report discipline's effective configuration without editing Claude Code settings. The plugin's whole configuration surface is native `userConfig`: three `sweep-all` batch-overlay options (`batch_exclude` / `batch_promote` / `batch_demote`) plus `do-your-research-deep`'s verification-depth default (`research_deep_verification`). Claude Code prompts for them when the plugin is enabled, stores non-sensitive options in user settings, and ignores `pluginConfigs` entries in project and local settings on current releases (>= 2.1.207). Check-only per the uniform setup contract's userConfig-only carve-out: this plugin's entire configuration surface is native `userConfig`, so `check` (the default and only action) verifies and reports, and reconfiguration routes through Claude Code's native flow, an `apply` here would have nothing to write except the `pluginConfigs` setup must never touch. Non-interactive: report and recommend; never block on a question. Official contract: . ## `check` (read-only, the only action) 1. Read the four rendered `${user_config.…}` values from the Variables block above (the three `batch_*` overlay options and `research_deep_verification`). Do not inspect or edit `settings.json`, `settings.local.json`, managed settings, or `pluginConfigs` directly. 2. **Empty or unexpanded is unset.** An option the user never configured does not reliably render empty, the literal `${user_config.…}` token can survive (a zero-config or headless install). Treat BOTH an empty value AND a surviving literal placeholder as unset (the key's own default applies); never read the literal token as a value. 3. For each set batch option, split on commas and report the parsed corrector names, and the net effect: `batch_exclude` drops those correctors from the batch, `batch_promote` runs those situational correctors every session, `batch_demote` gates those core correctors on relevance. With all three unset, report that the batch runs the tiers exactly as the correctors declare them. 4. **Validate the batch names against what is installed.** Glob the sibling corrector directories under this plugin's `skills/` and, for each name in an overlay, report: - a name in `batch_exclude` or `batch_demote` that matches no installed corrector: FAIL (typo or removed corrector); remediation: fix via the plugin configuration prompt; - the same name in `batch_exclude` and in `batch_promote`/`batch_demote`: contradictory; report it; - **`batch_promote` is situational-only** (read `metadata.discipline-batch`): promote only situational names. A promote naming a `never`-tier or `core` corrector, or a name that matches no installed corrector, is a **visible warning** and is not promoted, never stays out of the batch, core stays core, unknown is ignored. Do not report these as successful promotes. - a `batch_demote` naming an already-situational corrector, a no-op; INFO. 5. **Report the deep-research verification depth.** `research_deep_verification` sets `do-your-research-deep`'s default depth. Report the effective value: `tiered` (fan subagents out only over load-bearing items) or `full` (subagent-verify every item). An unset value, a surviving literal placeholder, OR any unrecognized string (not exactly `tiered` or `full`) all resolve to the `tiered` default. Report an unrecognized value as a WARN (typo; remediation: fix it via the plugin configuration prompt) that still falls back to tiered, never a hard failure. Note that an invocation argument to `do-your-research-deep` overrides this default per invocation. 6. **Full-batch prerequisite.** INFO: the batch's mid-session pass dispatches conversation-inheriting fork subagents. Fork mode is on by default in interactive sessions on Claude Code >= v2.1.232 (off by default in non-interactive `-p` and Agent SDK sessions; `CLAUDE_CODE_FORK_SUBAGENT` overrides either way: , re-checked 2026-08-26). `sweep-all` preflights this itself and degrades when the fan-out cannot inherit; that runbook owns the behavior; report the prerequisite here only so an unavailable fan-out reads as expected rather than as a misconfiguration, and do not restate what the degraded pass does. 7. To change or clear any value, direct the user to Claude Code's native flow, per the marketplace's plugin-reconfiguration convention, which owns the verified-version record (): interactive `/plugin configure discipline@` any time; headless, rerun `claude plugin install discipline@ -s user --config =` (repeatable per key) — against an already-installed plugin it prints `already installed` and still writes the value. Never uninstall to reconfigure: that drops the whole stored `pluginConfigs` entry, resetting every option to its manifest default. `-s` defaults to `user`, the only scope whose `pluginConfigs` these options load from (see above). Claude Code owns persistence. Do not hand-edit any `pluginConfigs` key. 8. Tell the user to rerun `check` after reconfiguration **in a fresh session**: the rendered `${user_config.*}` values are injected when this skill loads, so a same-session rerun still reports the OLD values. Report the OBSERVED effective values from that fresh run, never an unobserved change. ## Gotchas - **No `apply`.** Do not write the plugin cache, Claude Code user settings, or `pluginConfigs`, per the uniform setup contract (`docs/PLUGIN-PHILOSOPHY.md` "Setup is explicit and repeatable" in the marketplace repository). And `pluginConfigs` is the only thing an apply here could write, so there is no conforming apply to offer: reconfiguration is the native `/plugin configure discipline@` flow. - **Unexpanded token is not a value.** A surviving literal `${user_config.…}` means unset (the key's default applies). Parsing it as a corrector name or a depth value is the failure this check exists to prevent.