intelligence-extract-skilllisted

# Extract Skill Use when a workflow that ran during this session should become a reusable artifact — same sequence will be needed again by this user or by someone else using shared intelligence. Starts from observed session behavior instead of design-from-scratch. ## When to use this vs `intelligence-add-skill` - `intelligence-add-skill` — design from scratch / from codebase analysis - `intelligence-extract-skill` — extract from the conversation that just happened Both end at the same artifact format. Extract starts from observed behavior, so the steps already exist as real working procedure. ## Steps 1. **Identify the pattern from session**: list the concrete steps the assistant or user-and-assistant performed during the conversation. Include user decisions at each branch and assistant actions. 2. **Generalize**: strip session-specific details (file names, dates, specific phrasing), keep the repeatable structure. The artifact should work for the next instance of this task type, not just the one that ran. 3. **Determine artifact type**: - Multi-step workflow with concrete steps → **skill** - Behavioral preference / constraint / pattern to default to → **rule** (use `intelligence-learn-from-context` for single preferences from session) - Knowledge area / persona / expertise scope → **agent** 4. **Determine domain prefix** (for skill / agent): reuse the existing domain when one fits — list `<content-dir>/skills/` and `<content-dir>/agents/`. Derive from repo s