plugin-generatorlisted

# Plugin Generator Generate a distributable Claude Code plugin from the current project's dotforge configuration. The output is a standalone directory ready for `claude --plugin-dir` testing or marketplace submission. ## Input `$ARGUMENTS` may contain: - Output directory path (default: `./dotforge-plugin/`) - `--name <name>` to override plugin name (default: project directory name) ## Step 1: Validate source Verify the current project has dotforge configuration: - `CLAUDE.md` must exist - `.claude/settings.json` must exist - `.claude/rules/` should exist (warn if missing) If missing, error: "No dotforge configuration found. Run `/forge bootstrap` first." ## Step 2: Detect components Scan the project's `.claude/` directory and catalog: ``` Component scan: CLAUDE.md → will become commands/context.md .claude/rules/ → will become skills (one per rule with globs preserved) .claude/hooks/ → will become hooks/hooks.json + script files .claude/commands/ → will become commands/ .claude/agents/ → will become agents/ (if present) .claude/settings.json → will extract deny list → settings.json ``` Show the scan results and ask for confirmation before generating. ## Step 3: Generate plugin structure Two shapes — pick by component count: **Flat (single-skill plugin, v2.1.142+)** — when the plugin exposes ONE skill and no other components, put `SKILL.md` at the root. Claude Code surfaces it automatically since v2.1.142. Less boilerplate, no `skil