From decision-evaluation-framework
First-run onboarding for the decision-evaluation-framework plugin. Interview the user about output paths, preferred frameworks, default lens-bundles, and Google Drive export settings, then write the config to the plugin user-data directory. Run before first use of /decision:analyze.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin decision-evaluation-frameworkThis skill uses the workspace's default tool permissions.
One-time setup. Asks the user a small set of questions and writes a config file the rest of the plugin reads.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes multiple pages for keyword overlap, SEO cannibalization risks, and content duplication. Suggests differentiation, consolidation, and resolution strategies when reviewing similar content.
Share bugs, ideas, or general feedback.
One-time setup. Asks the user a small set of questions and writes a config file the rest of the plugin reads.
DATA_ROOT="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/decision-evaluation-framework"
mkdir -p "$DATA_ROOT"
Config lives at $DATA_ROOT/config.json. Never write to ~/.claude/ or to the plugin install directory.
Ask the user:
~/decisions/ (one folder per analysis: ~/decisions/<YYYY-MM-DD>-<slug>/).Decision-Log if they don't have one). Store the path; don't auto-init the repo unless they ask.frameworks/ directory of the plugin install). Ask them to pick a default set (5-10) that runs when /decision:analyze is invoked without a --bundle or --frameworks flag.quick — cost-benefit, pre-mortem, reversibility, regret-minimizationstrategic — swot, mcda, second-order, stakeholder-map, time-horizonpersonal — regret-minimization, ten-ten-ten, reversibility, inversioncrisis — ooda, cynefin, pre-mortem, reversibilityfull — all 20 frameworks
The user can accept these, edit them, or skip.gws-personal (default) or gws-dsrholdings. Ask which (or "none — local-only output").Decisions). Optional — if blank, export prompts each time.{
"version": 1,
"outputs": {
"mode": "local | repo",
"local_root": "/home/<user>/decisions",
"repo_path": null
},
"default_frameworks": ["cost-benefit", "pre-mortem", "..."],
"bundles": {
"quick": ["cost-benefit", "pre-mortem", "reversibility", "regret-minimization"],
"strategic": ["swot", "mcda", "second-order", "stakeholder-map", "time-horizon"],
"personal": ["regret-minimization", "ten-ten-ten", "reversibility", "inversion"],
"crisis": ["ooda", "cynefin", "pre-mortem", "reversibility"],
"full": ["<all 20>"]
},
"drive": {
"mcp_server": "gws-personal | gws-dsrholdings | null",
"default_folder": "Decisions"
},
"pdf": {
"author": "<name>"
}
}
Confirm the written config to the user. Tell them they can edit $DATA_ROOT/config.json directly later, or re-run /decision:onboard to redo the interview.