Use when the user wants to prepare for plan mode by gathering enterprise context. Triggers on "plan with glean", "prep for plan", "research before planning", "plan prep", or when starting strategic/architectural planning work.
Researches enterprise context from design docs and codebases before strategic planning sessions.
npx claudepluginhub gleanwork/claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
When users need to enter plan mode but want enterprise context first, use Glean to research design docs, similar implementations, stakeholders, and related systems.
Use plan prep when users:
Filter aggressively for relevant, current information.
Freshness Test
Relevance Test
Authority Test
Quality over quantity: 3-4 high-quality findings beat 10 weak ones.
Local tools only see your current repo. The plan-prep workflow searches your entire organization for:
This gives you enterprise context for better planning decisions.
| Research Need | Glean Tool |
|---|---|
| Find design docs, RFCs, architecture | search |
| Find similar code implementations | code_search |
| Find code owners and stakeholders | code_search + employee_search |
| Find related/dependent systems | code_search |
| Read full document content | read_document |
search "[task] architecture OR design doc OR RFC"code_search "[related components]" for similar solutionscode_search "[relevant systems] updated:past_month" + employee_searchcode_search for upstream/downstream componentsThe plan-prep command returns structured research organized as:
All with clear source citations so you can verify and dig deeper.
After reviewing the research:
Use /glean-code:plan-prep <task description> to start the planning preparation workflow.
/glean-code:codebase-context [system] - Get architectural context about a specific system/glean-code:code-owners [component] - Identify code owners and maintainers/glean-code:similar-code [pattern] - Find similar implementations across repos/glean-code:find-examples [API/pattern] - Find usage examplesExpert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.