/aim

Clarify the outcome you want. An aim is a change in user behavior, not a feature shipped. This is the first step in the Intent-Execution-Review loop.

The aim IS the abstraction. When you clarify what behavior you want to change, you're abstracting the business domain itself. Features are just the mechanism; the aim is why they matter.

When to Use

Invoke /aim when:

• Starting new work - Before diving into problem-statement or problem-space
• Scope feels fuzzy - You can describe what you're building but not why
• Multiple solutions seem valid - Aim clarifies which one actually moves the needle
• Work has drifted - Return to aim to check if you're still on track
• Team is misaligned - Shared aim surfaces hidden assumptions

Do not use when: You already have a crisp aim and need to explore the problem space or solution space. Move to /problem-statement or /problem-space instead.

The Aim Process