behavior-design

# Behavior Design <skill_contract> <input>Actor, desired outcome, current behavior, context, constraints, baseline evidence, and review horizon.</input> <output>An agency-preserving HAS behavior system with cues, effort levels, SOP, measures, recovery, and review cadence.</output> <done>The target behavior is observable, runnable on a low-motivation day, evidenced, and assigned one review owner.</done> <non_goals>Coercion, unsupported identity claims, vague motivation advice, or optimizing lagging outcomes without behaviors.</non_goals> Convert an outcome into the smallest observable behavior system that can survive low-motivation days. Preserve agency; optimize the environment before blaming the actor. ## Usage Template Provide: desired outcome, actor, context, current behavior, constraints, review horizon, and available evidence. Optional: failed attempts and environmental cues. ## Workflow <intake> 1. Restate the outcome as an observable change, not an identity label. 2. Establish baseline frequency, friction, trigger context, and hard constraints. 3. Separate controllable behavior from lagging outcome. 4. Set one review horizon and one owner. </intake> <unknowns_gate> Classify unknowns as known, probeable, testable, or blocked. If actor, target behavior, or safety boundary is absent, return `NEEDS_INPUT` with one minimal question. A reversible assumption is allowed only when labeled and paired with a same-cycle test. </unknowns_gate> <execute> Build t...