new-workspace

Provision Purchasing Workspace

Creates a new workspace for running a purchase decision or recommendation exercise. This plugin's commands (/purchasing:intake, /purchasing:research, /purchasing:rig-analyze, /purchasing:rec-more-like-this, etc.) are globally available once installed — this skill only provisions the data scaffold (CLAUDE.md, spec.md, context/, memory/, etc.) that those commands read from and write to.

Arguments

$ARGUMENTS is parsed as:

• First positional: workspace name (kebab-case, used as directory and GitHub repo name). Required.
• Second positional (optional): target parent path. Defaults to ~/repos/github/my-repos.
• --variant=<general-purchasing|tech-procurement|vendor-recommendations> (optional): which scaffold to copy. Default: general-purchasing.
• --local-only (optional): skip GitHub repo creation and push. Default: create a public GitHub repo and push.
• --private (optional): create the GitHub repo as private. Default: public.

Examples

/purchasing:new-workspace new-laptop-2026
/purchasing:new-workspace workstation-rig --variant=tech-procurement
/purchasing:new-workspace podcast-picks --variant=vendor-recommendations --private
/purchasing:new-workspace scratch-buy --local-only

Procedure

1. Parse arguments

Extract workspace name, target parent path, variant, and flags from $ARGUMENTS. If workspace name is missing, ask the user for it before proceeding.

2. Resolve the scaffold path

The bundled scaffold lives at ${CLAUDE_SKILL_DIR}/../../template/<variant>/. Confirm it exists. If the variant isn't general-purchasing, tech-procurement, or vendor-recommendations, tell the user which variants are available.

3. Read ambient facts

Read ~/.claude/CLAUDE.md if it exists. Extract OS, locale, timezone, currency, and user identity facts. These will personalise the workspace's CLAUDE.md at step 6.

4. Create the workspace directory

mkdir -p <target-parent>/<workspace-name>
cp -r ${CLAUDE_SKILL_DIR}/../../template/<variant>/. <target-parent>/<workspace-name>/

Do not copy any .claude/ tree. The plugin's primitives are global.

5. Personalise CLAUDE.md

Open the new workspace's CLAUDE.md and:

• Replace any placeholder identity / {{PROJECT_NAME}} tokens with workspace name and ambient facts.
• Add a short header noting the workspace name and variant.
• If ambient facts include OS / locale / currency, embed them so downstream commands can skip re-asking.

6. Prompt for workspace-specific facts

Ask the user only for facts this plugin can't infer:

• general-purchasing: what the user is buying (category + primary use case). Write into spec.md under "What I'm buying". Remind them they can run /purchasing:intake to complete the spec interactively.
• tech-procurement: the target machine label (e.g. workstation, gaming-pc). Remind them to run /purchasing:rig-setup then /purchasing:rig-profile to build hardware context.
• vendor-recommendations: the format(s) they want recommendations for (films, podcasts, books, etc.). Remind them to run /purchasing:rec-onboard to capture preferences.

7. Initialise git and (optionally) publish

cd <target-parent>/<workspace-name>
git init
git add .
git commit -m "Initial workspace from purchasing plugin"

Unless --local-only is set:

gh repo create <workspace-name> --<public|private> --source=. --push

Use --public by default, --private if flag was passed.

8. Print next steps

Tell the user:

• Workspace path.
• Variant chosen.
• Which plugin commands apply:
  • general-purchasing → /purchasing:intake, /purchasing:research, /purchasing:compare, /purchasing:recommend, /purchasing:market-check, /purchasing:load-preferences, /purchasing:save-preferences.
  • tech-procurement → /purchasing:rig-setup, /purchasing:rig-profile, /purchasing:rig-analyze, /purchasing:rig-compare, /purchasing:rig-recommend, /purchasing:rig-estimate.
  • vendor-recommendations → /purchasing:rec-onboard, /purchasing:rec-more-like-this, /purchasing:rec-log-feedback, /purchasing:rec-opml-ingest, /purchasing:rec-reading-list-ingest, /purchasing:rec-watch-history-ingest, /purchasing:rec-list.
• Reminder that the workspace is data — it can be deleted or moved freely without losing the plugin's commands.

Notes

• The scaffold path must be resolved via ${CLAUDE_SKILL_DIR}/../../template/ (not ${CLAUDE_PLUGIN_ROOT} — that variable isn't exported in skill bash injection, only in hooks/MCP).
• Never copy .claude/commands/, .claude/agents/, or .claude/skills/ into the new workspace. If the user wants workspace-local overrides, they can add them manually later.
• Don't hard-code any personal paths or identifiers here — everything comes from user memory or prompts.