From capture-plan
Display all configuration options with their effective value and which config layer set them.
How this skill is triggered — by the user, by Claude, or both
Slash command
/capture-plan:config-printThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Display every capture-plan config option, its current effective value, and which layer provided it.
Display every capture-plan config option, its current effective value, and which layer provided it.
CLAUDE_CWD="$PWD" bun ${CLAUDE_PLUGIN_ROOT}/hooks/print-config.ts
Parse the JSON output. It contains:
options — array of objects with key, value, and sourceconfigPaths — object with plugin, user, and project file paths (resolved for the current platform)warnings — optional array of { key, table, layer } entries flagging top-level scalar keys found scoped under a nested table (typically a TOML placement bug — the value is still recovered)Render a markdown table with these columns:
| Option | Value | Source |
|---|
For each entry in options:
plan.path)(not set) for null values.default, plugin, user, projectAfter the table, extract and display the resolved paths from the JSON response under configPaths:
"configPaths": {
"plugin": "...",
"user": "...",
"project": "..."
}
Display as:
configPaths.pluginconfigPaths.user (auto-resolved for the current platform)configPaths.project (or (not set) if outside a project)If warnings is present and non-empty, render a ## Warnings section after the paths. For each entry, display:
- `<key>` found under `[<table>]` in <layer> TOML — value was recovered to top level. Move the key out of the table to silence this warning.
Skip the section entirely when warnings is absent or empty.
npx claudepluginhub kriswill/capture-plan --plugin capture-planCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.