scaffold-simulation

name	scaffold-simulation
description	Create a new geopolitical-forecasting simulation workspace by cloning one of the registered upstream templates. Use when the user wants to "start a new geopol simulation", "set up a forecast", "scaffold a forecasting run", or asks which simulator template to use. Interactively presents the template registry with cost/depth tradeoffs, clones the chosen template into a new workspace, wires the .env file, seeds a scenario.md, and drops a .template-id sentinel.
allowed-tools	Bash, Read, Write, Edit, Glob

Scaffold a new simulation workspace

Creates a fresh workspace for one geopolitical-forecasting simulation, based on a chosen upstream template.

Inputs to gather

1. Forecast question — the scenario the user wants to forecast (e.g. "How will the X conflict evolve over the next month?"). Used to seed scenario.md.
2. Template choice — pick from templates/registry.json in the plugin. Read the registry, present each template with its name, description, and tradeoff blurb (the tradeoff field exists specifically so the user can make an informed choice). Default to asking — only auto-pick if the user has already named a template.
3. Workspace name — short slug for the workspace directory. Default: a slug derived from the question + today's date.
4. Workspace location — default to ~/repos/github/my-repos/<workspace-name>/. Confirm before creating.

Steps

1. Read the registry. Load templates/registry.json from the plugin install dir. List the available templates.
2. Prompt for template choice. Show the user the name + tradeoff for each. Wait for the choice unless one was named in the user's request.
3. Clone the template. git clone <repo> into the chosen workspace path. Use the default_branch from the registry entry.
4. Wire .env from 1Password. The registry's env_vars list names the required keys. For each, fetch from 1Password (use the op-vault:op-get skill or op read directly). Write to .env in the workspace root. Do NOT echo the values.
5. Run install commands. Execute the registry's install_commands array in the workspace dir (e.g. pip install -e . or uv sync).
6. Drop the sentinel. Write the registry's id to .template-id at workspace root. This is what every other skill in this plugin uses to dispatch.
7. Seed scenario.md. Write a short markdown file capturing: the forecast question, the chosen template (with its tradeoff blurb), the date scaffolded, and any horizon/grounding overrides the user mentioned. This is for the user's reference, not consumed by the templates themselves.
8. Register with runstore (if configured). Read $CLAUDE_USER_DATA/geopol-sim/config.json (resolution: ${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/geopol-sim/config.json). If a runstore path is set, append the workspace path to the registered-workspaces list there. If no runstore is configured, mention it and offer to run setup-runstore.
9. Report back. Workspace path, template chosen, env keys wired, what to run next (/run-simulation).

Notes

• The plugin never vendors template code — it always clones fresh from upstream. To pull updates into existing template clones, use update-templates.
• If the env key isn't found in 1Password, prompt the user; don't fabricate placeholder values.
• The .template-id sentinel is the contract every other skill relies on. Don't omit it.