lead-acelisted

# Lead-Ace - General Catch-All & Onboarding Skill The primary entry point for LeadAce. Three behaviors: 1. **Overview mode** (no argument): version + project list + skill catalog + suggested next step. 2. **Free-form mode** (text argument): classify intent, answer directly or delegate to a specific skill. 3. **Onboarding chain** (URL argument or first-time user): run env check + strategy drafting end-to-end so the user can go from "just installed the plugin" to "ready for `/daily-cycle`" in one command. After this skill, day-to-day use needs only `/daily-cycle` (which itself fans out to `/check-results`, `/evaluate`, `/outbound`, and `/build-list` when prospects run low). Other skills (`/setup`, `/strategy`, `/build-list`, `/outbound`, `/check-results`, `/evaluate`, `/import-prospects`, `/match-prospects`, `/setup-cron`, `/delete-project`) remain available as advanced shortcuts and as routing targets for this skill. **Before starting:** `Read` `${CLAUDE_PLUGIN_ROOT}/references/workspace-conventions.md` and follow the cross-cutting conventions there (data storage, MCP error handling, document writes, output discipline). ## Steps ### 1. Gather Context (always) Run these in parallel: - **Plugin version**: `Read` `${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json` and take `version`. - **Server version + min plugin**: `mcp__plugin_lead-ace_api__get_server_version` -> `{ serverVersion, minPluginVersion }`. - **Project list**: `mcp__plugin_lead-ace_api__list_projects` (may b