intent-framed-agent — Claude Code skill: frame the task

What intent-framed-agent does

It kicks in when the conversation stops being a plan and turns into code changes. The skill asks for a frame: the outcome, the approach, what sits out of bounds, how done gets verified. Five fields, one or two sentences each. After that the agent works inside that frame.

At natural checkpoints the skill looks for drift: before a new area or file, before a new logical chunk. When something sits outside the frame, an Intent Check appears in chat and asks whether the turn was deliberate or accidental creep. Once the work stops, a short resolution follows: delivered, pivots acknowledged, items still open. A session can hold several frames, but the current one closes before the next opens.

Use it on code that changes program behaviour. Research, plan-only talks and docs are out of scope, and trivial edits like a rename skip the whole frame. If session-context is installed, the skill queries it right after the first frame; without it the skill runs alone. Entire is checked with entire status, and where that command is missing the check is skipped quietly rather than blocking anything.