neo-sub-agent

# Neo Sub-Agent Use this skill to design and generate focused sub-agent definitions for developer CLIs. Keep the user in control of scope, permissions, and target clients. ## Core Rule Do not invent client-specific schema. If the requested CLI, field, or file location is not documented in `references/client-adapters.md` or discoverable in the project, state the missing fact and generate only a neutral blueprint. ## Workflow ### 1. Perceive 1. Inspect the project before asking questions: - Existing agent definitions: `.claude/agents/`, `.codex/agents/`, `.github/agents/`, `.agents/skills/`. - Project guidance: `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `.github/copilot-instructions.md`. - Related skills or conventions in `skills/`, `.agents/skills/`, `.github/skills/`, `.claude/skills/`, `.codex/skills/`. 2. Identify the target clients from the user request or project evidence: `claude`, `codex`, `copilot`, `agy`, or multiple. 3. If multiple clients are plausible and the request does not specify one, ask one concise question before writing files. ### 2. Decide Whether a Sub-Agent Fits Read `references/sub-agent-design.md` when the request involves architecture, multiple agents, or tradeoffs. Use a sub-agent when at least one is true: - The work produces verbose logs, search results, or file reads that should not pollute the main context. - The work is a repeated specialist role such as code review, planning, test execution, research, migration analysis, or docs veri...