enmanuelmag/agent-harness-kit

AHK Ask answers read-only questions about a codebase, such as where something lives, whether a feature exists, or how a path works. It is used when you need to inspect code without creating tasks or changing files.

AHK Consultant provides lightweight technical advice or review on an approach, idea, or change. It uses read-only context gathering and does not create tasks or track harness work.

AHK Test designs, writes, and runs behavior-focused tests for an objective or existing code. It writes test files only and reports evidence without creating harness tasks or changing production code.

AHK Triage performs read-only investigation of a bug or unexpected behavior and returns a structured diagnostic report. Use it when you need likely causes, affected files, and concrete fix ideas without creating tasks or tracking work.

Agent Consultant gives technical advice or review on an approach, idea, or change. It is used for lightweight consultation without creating tasks or tracking harness work.

Ahk Review previews a code review against a ticket or objective, including semantic checks for name-versus-behavior mismatches. Use it when you need a read-only rubric before official review.

Ahk Review previews how a code change aligns with a ticket or objective, including semantic checks on whether names match behavior. It is used for read-only review guidance without mutating harness state.

Ahk Test designs, writes, and runs behavior-focused tests for an objective or existing code. It writes test files only and reports evidence, without creating tasks or changing harness state.

Ahk Triage analyzes a bug or unexpected behavior and produces a structured diagnostic report. Use it when you need root-cause investigation without creating tasks or tracking harness work.

Ask Codebase answers read-only questions about a codebase, such as where something lives, whether a feature exists, or how a part works. It maps relevant files and explains the code without creating tasks or changing files.

Use Case Technical Spec turns an approved use-case specification into a linked technical specification. It is used to research dependencies, compatibility, risks, and implementation plans before approval and persistence.

Use Case To Technical Spec turns an approved use-case specification into a linked technical specification. It is used to research the codebase, capture compatibility and dependencies, and save a validated plan for approval.

Use Cases guides a lightweight discovery conversation to define or refine an approved non-technical specification. Use it when capturing goals, flows, rules, edge cases, and acceptance criteria before technical design.

Use Cases guides an iterative discovery conversation to define or refine an approved non-technical specification for a feature, change, refactor, or user journey. It is used before technical design to capture goals, flows, rules, boundaries, and acceptance criteria.