neo-agent-harnesslisted

# Agent Harness Architect Skill ## Trigger On - The user asks to design or improve an AI agent development workflow. - The user wants coding agents to be more reliable, safer, or easier to supervise. - The user asks for AGENTS.md, skills, tests, CI, hooks, review loops, or project rules to be planned together. - The task is about harness engineering, agent harnessability, feedback loops, or "humans on the loop". ## Core Principle Treat agent-assisted development as a controlled engineering system. Do not only improve prompts; design the guides, sensors, verification steps, and human decision points that let agents work with higher confidence. Use this skill for planning first. Do not modify files unless the user explicitly asks for implementation after the harness plan is clear. ## Perceive 1. Inspect the repository before asking questions: - Project instructions: `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `.github/copilot-instructions.md`. - Skill or prompt assets: `skills/`, `.codex/skills/`, `.claude/skills/`, `.github/skills/`. - Validation commands: `package.json`, `pyproject.toml`, `Makefile`, CI workflow files, build scripts. - Safety and governance: hooks, linters, formatters, secret scanners, dependency scanners. - Existing documentation: README, architecture docs, ADRs, testing docs, contribution docs. 2. Identify the project type, primary languages, current test surface, CI status, and release/deploy path. 3. Separate discoverable repository facts fr