analyze-reference-repolisted

# analyze-reference-repo Analyze a **different** repository (a competitor, a reference implementation, or a project the user admires) and produce a structured document that: - maps what the reference does well, - compares it against **this** project, - classifies each finding (adopt / adapt / reject / already-have), - proposes concrete adoption items, - optionally generates a roadmap draft for the adopt items. **Not** for analyzing the current project — use `/project-analyze` for that. **Not** for importing external skills wholesale — out of scope for this package; fork the reference repo or maintain the content in your own. ## Inputs The user provides a repository URL. Accept: - Full GitHub URL (`https://github.com/owner/repo`) - `owner/repo` shorthand - A raw archive URL (zip/tar) for private or mirrored repos Optional arguments: - `--focus=<area>` — restrict analysis to one axis (e.g. `installer`, `skills`, `mcp`, `governance`, `ci`). Default: full-surface. - `--no-roadmap` — skip the roadmap-draft step. ## Steps ### 1. Confirm scope Before touching anything, ask: > Found reference: `<owner/repo>`. > > 1. Full comparison — all axes (default) > 2. Focused — one axis (I'll ask which) > 3. Quick scan — README + top-level layout only > 4. Cancel Wait for the user's choice. ### 2. Fetch the reference surface Do **not** clone or execute the target repo. Fetch only: - `README.md`, `AGENTS.md`, `CHANGELOG.md`, `LICENSE` - `package.json` / `composer.json` / `pypro