keyword-expansion

Skill: keyword-expansion

Triggers & routing

• Trigger: keyword expansion, synonyms, exclusions, queries.md, keyword expansion, synonyms, exclusion terms.
• Use when: Insufficient search coverage/excessive noise, or many topic aliases, requiring systematic expansion and convergence of search terms.
• Skip if: queries.md Coverage can already be reliably detected (no need to expand scope and cause subsequent cost explosion).
• Network: none.
• Guardrail: Keep the number of queries controllable; clarify exclusions; avoid "infinite expansion".

Goal

• Improve recall/precision of queries.md without drifting scope.

Inputs

• queries.md
• Optional: DECISIONS.md scope notes

Outputs

• Updated queries.md

Procedure (MUST FOLLOW)

1. Extract the current topic scope and exclusions.
2. Propose keyword expansions (synonyms, related terms, acronyms) and add explicit exclusions for common false positives.
3. Update queries.md with a clear “why” note for each change.

Acceptance criteria (MUST CHECK)

• queries.md contains updated keywords and excludes.
• Changes do not contradict DECISIONS.md scope constraints.

Troubleshooting

Issue: keyword expansion causes scope drift

Fix:

• Re-read DECISIONS.md scope notes and add explicit exclusions in queries.md for common false positives.

Issue: query count explodes and becomes unmanageable

Fix:

• Keep a small set of high-signal queries; merge synonyms into the same query where possible instead of adding many near-duplicates.