dev-companionlisted

# Dev Companion (WHAT) — general layer (L2) This skill is the **general** dev companion for work. It does **not** replace **`assistant`** (orchestrator); it **sits above** workflows and names **what to invoke next**. **Language:** English for ticket comments, PR text, and user-facing outputs when this companion drives delivery work. ## Layering | Layer | Skill | Role | | --- | --- | --- | | L1 | **assistant** | Repo inspection order, conflict resolution, fallback | | **L2 (this skill)** | **dev-companion** | Companion framing: modes, gates, delegation for client work | | L3 | **Workspace pack overlay** | Client/account-specific context loaded from `~/.ai-workspace/packs/` | If engagement triggers match, load the appropriate **workspace pack overlay** first, then proceed with **workflow-generic-project**. Do not mix multiple workflow drivers on the same task. ## Mode selection - **Default** for /client delivery: use **workflow-generic-project** for phased delivery. - If the user mentions an engagement, ticket prefix, or repo context → load the matching pack from the workspace (overlay) and apply its boundaries/gates. - If unclear → **ask** before applying L3. ## Delegation (HOW is in other skills) | Need | Delegate to | | --- | --- | | Discovery, AGENTS conflict handling | **assistant** | | Generic client delivery phases | **workflow-generic-project** | | Planning / default workflow / validation | **planning** / **development-workflow** | | Work items, incidents, meet