Product & engineering
Test Gap Suspicions
Identify behavior with missing or weak test evidence.
Configure this skill
The page and the file follow your answers.
CRM
Email
Chat
Documents
Calendar
Project tools
6 of 6 systems connected
KeepDirectMissing
Your assistantSKILL.md
Download ↓
When to use it
Identify behavior with missing or weak test evidence.
What it covers
Inputs
Repository/ref, changed or critical behavior.
Result
Behavior-to-test matrix and prioritized test cases with evidence limitations.
What it uses
Project toolsSlackKeep memoryRead only
For developers
Retrieval instructions
Resolve people, accounts and projects by stable identifiers. Use only the sources this task needs. Cite the source and date for each finding. Keep source systems unchanged.
Data sources
GitHub, Linear, Slack, Keep memory.
Procedure
- Resolve inputs for Test Gap Suspicions: project_key, repo, issue_id, time_window. Default time window: current sprint / since last ship (override if caller provides time_window). Ask only for missing critical inputs.
- keep_memory_read for open tasks, decisions, and handoffs relevant to Test Gap Suspicions (filter out unrelated day-plan noise).
- Run keep_search with these skill-specific intents (keep meaning; adjust wording to corpus):