aim

Define a concrete user behavior change with current and desired states.

3|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/open-horizon-labs/skills --skill aim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aim
Source: https://github.com/open-horizon-labs/skills/tree/main/aim
Command: npx skills add https://github.com/open-horizon-labs/skills --skill aim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify and lock in the desired user behavior at the start of any work, ensuring teams align on outcomes rather than just features.

Core Features & Use Cases

  • Define and document a concrete aim that drives problem framing, execution, and review.
  • Provide a structured approach to map current vs. desired behavior, identify the mechanism, and establish measurable signals.
  • Enable session persistence and cross-skill continuity so future steps (problem-statement, solution-space, review) stay aligned.

Quick Start

Draft a clear aim statement for this task by following the four steps and save it to your session if you want to continue later.

Frequently Asked Questions about aim

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define a concrete user behavior change for project initiation?

To define a concrete user behavior change, map the current versus desired states, identify the mechanism driving the change, and establish measurable signals to ground execution and align outcomes.

What is the best way to align team workflow when project scope is fuzzy?

The best way to align workflow with a fuzzy scope is to lock in a crisp aim definition that frames the problem, sets guardrails, and establishes measurable signals to drive decision-making.

How do I create a persistable session artifact for product management alignment?

Create a persistable session artifact by documenting your aim definition, including current and desired behavior states, to maintain cross-skill continuity and keep future steps aligned.

Can I use this aim definition approach to re-align after project drift?

Yes, you can apply aim definition to re-align after project drift by re-establishing the desired user behavior, verifying the mechanism, and reviewing measurable signals to correct execution.

Does defining an aim require setting up specific guardrails and measurable signals?

Defining an aim requires setting up guardrails and measurable signals to ensure the desired user behavior change is tracked accurately and execution stays within project boundaries.

Why does problem framing need a structured aim definition before execution?

Problem framing needs a structured aim definition before execution to ensure teams align on target outcomes rather than just features, preventing scope creep and grounding the workflow.