uat
Check the running app against the owner's request, blind to the plan, the diff and the Verify row. Use after a ticket is built, or from `/harness:uat N`, for FE, BE and FE+BE tickets.
Use when English text must be parsed without a human to resolve ambiguity â tool descriptions, error messages, inter-agent instructions, system prompts, status reports â and misreading has a real cost, or when text reads as dense, hedged, or easy to misparse. Triggers: disambiguate, STE100 rewrite, apply Simplified Technical English, plain-language rewrite, controlled-language rewrite, rewrite so an agent cannot misread this. Not for creative or marketing copy.
Run grilling or brainstorming in ownership mode. The owner answers each big decision first, then sees the agent's recommendation and a counter-argument. Use when the owner types /harness:own grill or /harness:own brainstorm. Not for autopilot or --no-ask runs.
If nothing struggled, say so and stop. Rules manufactured from a clean run make the harness worse.
Turn a brief (brief.md, prd.md, intent.md, notes) into GitHub issues, each built to pass harness:intake as READY, after one owner approval. Can group the new issues under a milestone. Use when the owner has a brief and wants tickets.
Auto-indexed from minhtran3124/agent-harness
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.