research
Research
Scan a codebase and produce a structured context map that all subsequent analytics skills consume.
When to Use
- Starting analysis on a project for the first time
- Before running
goal-definition,brainstorming,prd,architecture, orbreakdown - When switching to a different project or codebase
- When the codebase has changed significantly since the last context map
When NOT to use: The project already has a recent, accurate context-map.md in the artifact folder.
Input
- A codebase or project path (provided by user or detected from workspace)
- Check
references/context-sources.mdfor known project documentation files (docs/TechStack.md,docs/ProjectStructure.md). If they exist and are fresh, use them to pre-populate tech stack and structure findings — then focus scanning on patterns, conventions, rules, and health notes.
Output
More from olamedia/analytics-skills
analyze-project
Use when starting work on any project to produce or update living documentation (TechStack.md, ProjectStructure.md) that bootstraps context for any AI agent session. Run before any feature work, or periodically to keep docs current.
13humanizer
>-
12architect
>-
12goal-definition
Use when you have a raw idea or request and need to define a clear goal with success criteria before exploring solutions. Use when requirements are vague, when "what does done look like" is unclear, or when assumptions need surfacing.
11prd
Use when you have a chosen direction and need to formalize requirements into a Product Requirements Document. Use when user stories, acceptance criteria, and scope boundaries need to be written down before architecture or implementation.
10analyze
Use when you have a raw idea or request and want to run the full analytics pipeline automatically — from research through to an interlinked task list. Best for straightforward problems where the full pipeline can flow with minimal back-and-forth.
10