From sdlc-skills
Searches local KB, email, and Teams to find prior discussions, decisions, and commitments about a person or topic before you respond.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sdlc-skills:gathering-contextThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Find prior discussions, decisions, and commitments across channels — fast. Walk channels in cost order and stop early when you have enough.
Find prior discussions, decisions, and commitments across channels — fast. Walk channels in cost order and stop early when you have enough.
.knowledge/threads.json), Read it and Grep for the person's email and topic keywords.search-query with from:<email> AND <keywords> (and to:<email> variant).list-mail-messages + manual filter if search-query is unavailable.get-mail-message only for the top 3–5 hits — never bulk-read.find-chat by name → list-chat-messages for the matched chats with recent activity.tavily_search for public topics (announcements, vendor docs). Never web-search internal/private topics.Stop as soon as you have enough to answer the question. Don't exhaust every channel by default.
Max ~500 words. Facts, not essays.
## Context for <person> — <topic>
### Prior conversations
- [date] <channel>: <one-line summary>
- [date] <channel>: <one-line summary>
### Decisions & commitments
- <what was agreed, by whom, when>
### Related discussions
- <relevant context from other people/threads>
### Open items
- <anything unresolved or pending>
If nothing relevant exists, say so in one line. Never fabricate context.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub arozumenko/sdlc-skills --plugin test-automation-workflow