share

Share

Package a system or feature from your workspace for sharing. Deep-dives the system first, then produces a self-contained, beginner-friendly package with a Claude-guided installer that anyone can use.

Variables

target: $ARGUMENTS (describe the feature/system to share, e.g., "the daily brief system", "the data pipeline", "the client onboarding flow")

---

Stage 1: RESEARCH — Fully Understand the System

Goal: Map every piece of the system before writing a word.

Actions:

1. Parse the target description from the arguments
2. Search the codebase exhaustively for everything related:
   • Scripts and code — the actual implementation
   • Docs — any technical documentation
   • Commands (.claude/commands/) — slash commands involved
   • Skills (.claude/skills/) — skill definitions
   • Config (.env, .env.example) — required API keys and services
   • Database schemas — tables involved
   • Cron / scheduling — automation schedules
   • Dependencies (requirements.txt, package.json, imports in code)
3. Read every relevant file — understand inputs, processing, outputs, external dependencies, what's business-specific vs reusable
4. Build a system component map — every file, every external service, every API key, every scheduled job

Present:

System: {name}
Components:
  [x] {file/module 1} — {what it does}
  [x] {file/module 2} — {what it does}
  [x] {file/module 3} — {what it does}
  ...
External services: {list with whether each needs an API key}
API keys required: {count and list}
Database tables: {list or "none"}
Automation: {cron/launchd/manual/none}
Complexity: Simple (1-3 files) / Medium (4-10 files) / Complex (10+ files)

STOP and wait for confirmation. "Here's what I found. Anything I'm missing?"

---

Stage 2: SCOPE — Define What Ships

Goal: Determine what to include and who it's for. Keep this efficient — 2-3 questions max.

Actions:

1. Present the component list from RESEARCH as a checklist. Mark recommended components with [x] and optional ones with [ ]: