analyze
Analyze (Orchestrator)
Run the full analytics pipeline in sequence: research, goal definition, brainstorming, PRD, architecture, and task breakdown. Produces a complete set of interlinked artifacts from a raw idea.
When to Use
- A feature request or idea needs the full treatment: analysis through to task list
- The problem is straightforward enough that all 6 steps can flow in one session
- You want to minimize manual skill invocation and let the pipeline run
When NOT to use:
- The problem is complex or ambiguous — run skills individually with more deliberation at each stage
- Only one phase is needed (e.g., just need a PRD for existing requirements) — invoke that skill directly
- Upstream artifacts already exist — pick up from the appropriate skill in the chain
Input
- A raw idea, feature request, or problem description from the user
- A codebase to analyze (current workspace or specified path)
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.
10frontend-design
>-
10