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". - The user wants to design scheduled automations, cron-driven agent loops, or recurring agent tasks. - The user wants multiple agents to work in parallel and needs an isolation strategy (worktree isolation). - The user wants to design maker/checker separation (generation and verification by different agents). - The user wants to design external memory or cross-conversation state persistence for agents. - The user asks how to evolve from a harness to loop-driven development. ## 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. When the task involves automations, parallel agents, or continuous loops, extend the design to cover loop architecture: the scheduling, isolation, separation, integration, and state layers that let the harness run itself. Use this skill for planning first. Do not modify files unless the user explicitly asks for implementation after the harness plan is clear. ## P