onboard

name	onboard
description	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.

Onboard

One-time setup. Asks the user a small set of questions and writes a config file the rest of the plugin reads.

Resolve the data root

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.

Interview

Ask the user:

1. Where should decision analyses land?
   • Default: ~/decisions/ (one folder per analysis: ~/decisions/<YYYY-MM-DD>-<slug>/).
   • Alternative: a dedicated GitHub repo (suggest creating Decision-Log if they don't have one). Store the path; don't auto-init the repo unless they ask.
2. Which frameworks are your defaults? Show the full catalog (read 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.
3. Should I define any lens-bundles now? Suggest starter 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 frameworks The user can accept these, edit them, or skip.
4. Default Google Workspace MCP for Drive export? Options on Daniel's machine: gws-personal (default) or gws-dsrholdings. Ask which (or "none — local-only output").
5. Default Drive folder for uploaded analyses? A folder name or path inside Drive (e.g., Decisions). Optional — if blank, export prompts each time.
6. Author name for the rendered PDF. Default to the system user.

Write config

{
  "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", 
        
        
     
  
   
     
     
  
   
     
  

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.