goal-definition
Goal Definition
Take a raw idea or request and turn it into a clear, actionable goal with explicit success criteria, assumptions, and constraints.
When to Use
- You have a vague idea or user request that needs sharpening
- Before brainstorming approaches — define the "what" before the "how"
- Requirements are ambiguous or incomplete
- You need to align on success criteria before investing in design
- Assumptions are lurking but haven't been stated
When NOT to use: The goal is already crystal clear with written success criteria, or a goal-definition.md already exists and is still accurate.
Input
- Raw idea or request from the user
context-map.mdfrom the artifact folder (recommended but not required)- See
references/context-sources.mdfor additional project documentation that may provide context
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
>-
12prd
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.
10frontend-design
>-
10