AIM

Required entry skill when you are an AIM Developer working on an existing AIM Task and must read the task via AIM Server, validate it against the latest baseline, execute the worktree and PR lifecycle, report field facts, and complete the bound OpenCode session.

Strongly recommended when you need to clarify questions, converge directions and uncertainties, do design or orienting work, or answer open-ended questions before deciding how to proceed and producing a task spec, especially when key clarifications could change the route.

Coordinator decision entry for AIM Task Pool maintenance; form an approvable POST /tasks/batch operations plan from Manager output, latest baseline facts, current Tasks, and rejected Task feedback before applying atomic Task Pool writes.

当用户已经明确批准创建新的 AIM Task，且需要把稳定的用户意图整理成候选 Task Spec 并提交到 POST /tasks 时使用。

Use when judging how README claims compare to the latest origin/main baseline and the coordinator needs direction signals without task creation or execution decisions.

AIM Manager guidance for evaluating README goals against the latest baseline, defining iteration direction and Dimensions, and preparing Coordinator-consumable evaluation signals without creating tasks or executing work.

Use when a GitHub repository needs its merge settings, default-branch ruleset required checks, or PR auto-merge behavior verified or standardized with gh.

当需要在 AIM 仓库内实现新功能、修复缺陷、调整行为或补回归保护，并且必须在写实现前执行真实测试优先纪律时使用。

Use when validating whether an AIM Task Spec is still actionable against the latest baseline and the agent must distinguish waiting assumptions from true spec failure.

当 AIM Agent 需要新增、修改、迁移或评审测试时使用，确保测试保护行为语义而不是当前实现形状。

Use when starting AIM-related work to decide whether ask-strategy, Manager evaluation signals, Coordinator Task Pool maintenance, task creation, README evaluation, spec verification, developer execution, or repo setup guidance applies before any response or action.