@openhint/hintbook-qa-engineer

The official HINT vocabulary for qa engineers. The assistant derives cases from declared requirements; it never invents results or weakens expected behavior to match an implementation.

Measured performance and retrieval results live in the core benchmark report.

hint.yml
_.hint
vault-access/
├── _.hint
└── artifact.md.hint
elevator-control/
└── _.hint
shared/policy.hint

Installation

hint add @openhint/hintbook-qa-engineer
hint apply

Vocabulary

| Plan | plan, sut, env, strategy, exitcriteria | | Cases | case, precondition, step, expected, testdata, negative, edge, oracle | | Coverage | covers, severity, priority, defect | | Automation | automate, flaky | | Shared core | never, source, term, assumption, risk, decision, openquestion, checklist, style, example, good, bad, read, res, notes |

Natural plurals and long forms are included as keyword synonyms; profession search synonyms are declared in keywords/hintbook.json. Full reference: docs/keywords.md.

Output and framing

| Command | Result | | --- | --- | | hint <path> | Scoped profession knowledge only. | | hint --prompt <path> | Role header, scoped knowledge, verification footer. | | hint --standalone <path> | Prompt plus the complete tag glossary. |

Verifiable surfaces: case. These names are stable artifact identifiers and must appear verbatim.

Deterministic emit

The markdown pack emits reviewable test document structure without a model. A Gherkin pack emits plain .feature scenarios. Run hint emit <path> and gate CI with hint emit --check. Prose that templates cannot derive remains a marked hole.

Example

# plan vault-access

Declared context for the test document.

# never Invented details

The assistant derives cases from declared requirements; it never invents results or weakens expected behavior to match an implementation.

License

MIT