hb-sk-hound

Files (1)

• SKILL.md

SKILL.md (first lines)

# hb-sk-hound

Knowledge contract for **The Hound**. Follow clues in the tree. Very cheap. Then stop.

## Load

The clue list from The Hunter is the scent. Do not load [[PRD]] or [[INTERFACES]]. Graph: [[adr-35-graphify]] first. Graph absent → Grep the clues ([[adr-35-graphify]] rule 5).

## Order

1. **Graphify.** `query_graph` per clue (or one query that names them). `get_neighbors` when a hit is a leaf. Record path + symbol.
2. **Grep / Read** only those files (or Grep-first if no graph). Keep excerpts short.
3. **Catalog.** Strongest scent first. Cap ~8 rows. Stop.

No `Bash`. No `gh`.

## Catalog

```
HOUND
clues: [tag, ...]
hits:
  - path: <repo-relative, full from repo root>
    symbol: <function/class/heading or —>
    lines: <start-end>
    excerpt: <≤8 lines>
    clue: <which clue hit>
    why: <one line>
```

Paths are complete. The Hunter must be able to evaluate without opening the file.

## Quick exit

A GitHub issue history question is The Hawk. A bulletin is The Hunter. Empty catalog + one line beats a long run.

## Do not

- `gh` or `git`.
- Dump whole files. Follow clues that were not in the brief.
- Agent anyone. Load area-owner skills.
- Write a triage score.

## Instantiation

This is a template skill: rename the folder to `{{prefix}}-sk-hound`.
See [[ONBOARDING]] and [[CLONE]].

From kodexArg/harness-base, MIT.

More from kodexArg/harness-base