Skip to content
Back to skills

Ahk Use Case Tech

ASecurity

Turn an approved use-case, feature, or fix into a linked, evidence-backed technical specification.

  • 182 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 7, 2026
ai-agentsapidocumentation

Works with

  • cli
  • api
  • mcp

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 7, 2026

npx -y skills add enmanuelmag/agent-harness-kit --skill ahk-use-case-tech --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ahk Use Case Tech?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ahk Use Case Tech
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/enmanuelmag-ahk-use-case-tech-agent-harness-kit/badge)](https://www.skillsdirectory.com/skills/enmanuelmag-ahk-use-case-tech-agent-harness-kit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ahk-use-case-tech
description: Turn an approved use-case, feature, or fix into a linked, evidence-backed technical specification.
---

## Entry gate

Start by locating the requested source with `specs.list` or `specs.search` and reading it with `specs.get`. Stop unless it is an approved `use-case`, `feature`, or `fix`; help resolve it with the corresponding discovery skill 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.

After the technical investigation produces a complete first synthesis, create or update a `technical` draft through structured MCP tools with `sourceSpec` pointing to the approved source, then run `specs.validate`. Keep the draft reviewable and editable through MCP; transition it to `approved` only after explicit user confirmation. A technical spec that is `needs-reconciliation` must not be used as an implementation plan until reconciled and approved again.

Files in this skill

  • SKILL.md1.8 KB
  • resources/technical-template.md362 B
  • resources/technical-workflow.md301 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.