Skill
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.
@enmanuelmagView SkillAgent Orchestration
Skill
/ahk-use-case-tech
Turn an approved use-case specification into a linked, evidence-backed technical specification.
Install
$ npx -y skills add enmanuelmag/agent-harness-kit --skill ahk-use-case-tech --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ahk-use-case-tech
Context preview
The summary Claude sees to decide when to auto-load this skill.
Turn an approved use-case specification into a linked, evidence-backed technical specification.
SKILL.md
ahk-use-case-tech.SKILL.mdname: ahk-use-case-tech
description: Turn an approved use-case specification into a linked, evidence-backed technical specification.
Entry gate
Start by locating the requested use-case with `specs.list` and reading it with `specs.get`. Stop if it is not an `approved` `use-case`; help resolve it with `ahk-use-cases` first.
Read [the technical workflow](resources/technical-workflow.md) before analysis and [the technical template](resources/technical-template.md) before saving.
Investigation
Inspect the relevant codebase before proposing technical work. For every library, framework, SDK, API, CLI, cloud service, version, compatibility, configuration, or migration question: identify installed versions from manifests and lockfiles, query Context7 and the Mintlify documentation index when available, then use primary documentation for gaps. Record compatibility, upgrade need, new dependency need, and evidence. Do not treat an unverified assumption as a decision.
Proposal and persistence
Define affected boundaries, contracts and data flow, alternatives and rationale, compatibility findings, dependencies, rollout or migration, risks, validation, and a phased implementation plan. Link related specifications with `specs.link`; use `depends-on`, `extends`, `supersedes`, `conflicts-with`, or `informs` precisely.
Present the technical proposal for user approval before writing it. Once approved, create or update a `technical` specification through structured MCP tools with `sourceSpec` pointing to the approved use-case, then run `specs.validate`. A technical spec that is `needs-reconciliation` must not be used as an implementation plan until reconciled and approved again.
Read more
name: ahk-use-case-tech description: Turn an approved use-case specification into a linked, evidence-backed technical specification.
Entry gate
Start by locating the requested use-case with `specs.list` and reading it with `specs.get`. Stop if it is not an `approved` `use-case`; help resolve it with `ahk-use-cases` first.
Read [the technical workflow](resources/technical-workflow.md) before analysis and [the technical template](resources/technical-template.md) before saving.
Investigation
Inspect the relevant codebase before proposing technical work. For every library, framework, SDK, API, CLI, cloud service, version, compatibility, configuration, or migration question: identify installed versions from manifests and lockfiles, query Context7 and the Mintlify documentation index when available, then use primary documentation for gaps. Record compatibility, upgrade need, new dependency need, and evidence. Do not treat an unverified assumption as a decision.
Proposal and persistence
Define affected boundaries, contracts and data flow, alternatives and rationale, compatibility findings, dependencies, rollout or migration, risks, validation, and a phased implementation plan. Link related specifications with `specs.link`; use `depends-on`, `extends`, `supersedes`, `conflicts-with`, or `informs` precisely.
Present the technical proposal for user approval before writing it. Once approved, create or update a `technical` specification through structured MCP tools with `sourceSpec` pointing to the approved use-case, then run `specs.validate`. A technical spec that is `needs-reconciliation` must not be used as an implementation plan until reconciled and approved again.
Ships withagent-harness-kit
A provider-agnostic scaffolding kit for running structured multi-agent workflows in your codebase.
Get the whole plugin
Stats
181
Stars
9
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
3d ago
Last commit
4mo ago
Created
Repo: enmanuelmag/agent-harness-kit
Other skills on agent-harness-kit.
@enmanuelmagView SkillSkill
ahk-consultant
Get technical advice or review on an approach, idea, or change. References available skills for best practices. No tasks created, no harness tracking.
@enmanuelmagView SkillSkill
ahk-review
Preview a code review against ticket/objective alignment, with deep semantic (name-vs-behavior) analysis. No tasks created, no harness tracking.
@enmanuelmagView SkillSkill
ahk-test
Design, write, and run behavior-focused tests for an objective or existing code. Writes test files only and reports evidence. No tasks created, no harness…
@enmanuelmagView SkillSkill
ahk-triage
Triage a bug or unexpected behavior. Deep diagnostic analysis with structured report. No tasks created, no harness tracking.
@enmanuelmagView SkillSkill
ahk-use-cases
Define or refine a feature, change, refactor, or user journey as an approved non-technical use-case specification.
@enmanuelmagView Skill