plan-prep
Planning Preparation via Glean
When users need to enter plan mode but want enterprise context first, use Glean to research design docs, similar implementations, stakeholders, and related systems.
When This Applies
Use plan prep when users:
- Want to research before entering plan mode
- Are planning architectural or strategic changes
- Need to understand related systems before designing
- Want to identify stakeholders and code owners early
- Phrase it as: "plan with glean", "prep for plan", "research before planning", "plan prep"
BE SKEPTICAL
Filter aggressively for relevant, current information.
Freshness Test
- ✅ CURRENT: Updated in past 6 months
More from gleanwork/claude-plugins
code-exploration
Use when the user asks about internal code, implementations, patterns across repositories, or needs to understand how something is built. Triggers on "how is X implemented", "where is the code for", "find the implementation of", "what repos contain", "who wrote the code for", or code architecture questions about internal systems.
15glean-tools-guide
Use when Glean MCP tools are available and you need guidance on which tool to use, how to format queries, or best practices for enterprise search. This skill provides tool selection logic and query optimization for Glean integrations. Auto-triggers when mcp__glean tools are being considered.
14activity-synthesis
Use when the user asks about their recent work, what they've been doing, their contributions, or needs to recall past activity. Triggers on phrases like "what have I been working on", "what did I do last week", "my recent activity", "what have I accomplished", "summarize my work", "what projects am I on", or when the user needs to recall or reflect on their own work.
13project-awareness
Use when the user asks about project status, ownership, or context. Triggers on phrases like "status of X project", "who owns Y", "what's happening with Z", "project update", "where does the project stand", "what's the state of", "who's working on", or when needing quick project context without a full analysis.
13people-lookup
Use when the user asks about people, employees, team members, org structure, or expertise. Triggers on phrases like "who works on", "who is responsible for", "who owns", "find someone who knows", "who should I talk to", "who reports to", "team members", "org chart", or any question starting with "who" about the company.
12enterprise-search
Use when the user asks about company documents, internal wikis, policies, specifications, design docs, RFCs, or enterprise knowledge. Triggers on phrases like "find the doc about", "what's our policy on", "where is the spec for", "company guidelines", "internal documentation", or when searching for information that would be in enterprise systems rather than the local codebase.
12