aim
Installation
SKILL.md
/aim
Clarify the outcome you want. An aim is a change in user behavior, not a feature shipped. First step in Intent-Execution-Review.
The aim IS the abstraction. Clarifying what behavior to change abstracts the business domain itself. Features are mechanism; the aim is why they matter.
When to Use
- Starting new work — before problem-statement or problem-space
- Scope feels fuzzy — you can describe what but not why
- Multiple solutions seem valid — aim reveals which moves the needle
- Work has drifted — check alignment
- Stakeholders are misaligned — surfaces hidden assumptions
Skip when: You already have a crisp aim. Move to /problem-statement or /problem-space.