forge-initlisted

# forge-init ## When to Use Use this skill whenever the user wants to: - Start using Forge in a project - Initialize the Forge pipeline in a new or existing project - Says "init", "initialize", "set up Forge", or "start using Forge" - Describes starting a new project they want orchestrated - Passes `--dry-run` to preview what would be created without writing files ## Steps 1. Parse `$ARGUMENTS` for `--dry-run`. If present, set `DRY_RUN=true`. If the user passed `--type <profile>`, capture that as `OVERRIDE_TYPE`. 2. **If `DRY_RUN`**: - Run `bash ${CLAUDE_PLUGIN_ROOT}/scripts/init-pipeline.sh --dry-run` - Present the plan verbatim. The final line reads "Re-run without --dry-run to apply." - **Stop here. Do not proceed to step 3 or any subsequent step.** Wait for the user to explicitly confirm they want to apply the plan before doing the real init. 3. Run the real init in manifest mode to capture what was created: - `bash ${CLAUDE_PLUGIN_ROOT}/scripts/init-pipeline.sh --manifest-only` - The manifest is JSON: `{dry_run: false, root: "<abs path>", created: [...], skipped: [...]}` - Parse the JSON. The `created` array length tells you how many files were written; the `skipped` array shows pre-existing files that were left alone. 4. Detect the project type (skip if `OVERRIDE_TYPE` was set): - Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/detect-project-type.py --cwd .` - The output is JSON with a `project_type` (or `assigned_profile`) field, plus a `confid