ahk-ask
Ask a question about this codebase — where is X, does Y exist, how does Z work. Read-only. No tasks created, no harness tracking.
Turn an idea or Jira request into a reviewable, evidence-backed feature specification.
Claude Code
$ npx -y skills add enmanuelmag/agent-harness-kit --skill ahk-feature --agent claude-code
Codex
$ npx skills add enmanuelmag/agent-harness-kit --skill ahk-feature -a codex -y
Cursor
$ npx skills add enmanuelmag/agent-harness-kit --skill ahk-feature -a cursor -y
Gemini CLI
$ npx skills add enmanuelmag/agent-harness-kit --skill ahk-feature -a gemini-cli -y
GitHub Copilot
$ npx skills add enmanuelmag/agent-harness-kit --skill ahk-feature -a github-copilot -y
OpenCode
$ npx skills add enmanuelmag/agent-harness-kit --skill ahk-feature -a opencode -y
Windsurf
$ npx skills add enmanuelmag/agent-harness-kit --skill ahk-feature -a windsurf -y
name: ahk-feature description: Turn an idea or Jira request into a reviewable, evidence-backed feature specification.
Read [the feature workflow](resources/feature-workflow.md) before discovery and [the feature template](resources/feature-template.md) before saving.
After the required questions and project evidence produce a complete first synthesis, create or update a `feature` draft with structured specification MCP tools. Use `specs.list` and `specs.search` to find related context, `specs.get` to read it, and `specs.validate` after every write. Keep drafts reviewable and editable through MCP; transition to `approved` only after explicit user confirmation.
Do not choose an implementation design. Offer `ahk-spec-tech` only after this feature is approved and the user asks for technical design.
The MCP assigns new documents a `YYYY-MM-DD-<slug>.md` filename using the UTC creation date. Use the returned `filePath` (relative to the configured docs directory) to locate the artifact; do not reconstruct or rename it. The prefix belongs only to the physical filename: keep the logical slug, title, source references, and relationships unchanged. Existing files retain their paths on every update.
Agent Harness Kit (AHK) gives AI coding providers a shared workflow for documents, tracked tasks, handoffs, and health evidence. It supports Claude Code, Codex CLI, Cursor, Grok Build, OpenCode, and OpenCode V2. AHK supplies structure and records.
Ask a question about this codebase — where is X, does Y exist, how does Z work. Read-only. No tasks created, no harness tracking.
Get technical advice or review on an approach, idea, or change. References available skills for best practices. No tasks created,…
Explain how to use and operate Agent Harness Kit= workflows, providers, MCP, health gates, and upgrades. Read-only; does not…
Turn a reported defect or Jira issue into a reviewable, evidence-backed fix specification.
Preview a code review against ticket/objective alignment, with deep semantic (name-vs-behavior) analysis. No tasks created, no…
Turn an approved spec, feature, or fix into a linked evidence-backed technical specification.
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by…
Create a new Architecture Decision Record with sequential numbering and AgentDB registration