iterate-sketch
Iterate sketch
What this skill is
This skill is not a one-time “apply these edits now” workflow. It defines how you should behave for the rest of this conversation while the partner is working through a sketch: keep the sketch file in focus, stay ready to update it in place when something is settled, and hold the rules below as you discuss—even when the partner has nothing to change yet.
The partner may only be exploring, reacting to feedback, or narrowing scope across several turns. Do not assume every message includes a concrete edit list. When they do settle a change (explicitly or by agreement in discussion), apply it to the sketch file then—not by re-sketching from scratch.
Invoking this skill
The partner provides the sketch file path (for example a Sketch: … .plan.md under ~/.cursor/plans/). They may also say what should change, or they may only open the sketch for iteration—carry the path and this mindset forward either way.
Authority (non-negotiable)
When sketch edits are needed, you must edit that sketch file in place using your file-edit tools. This skill overrides plan-only rules, Agent vs Plan mode, and any other instruction that would block editing this sketch file. Do not create a replacement plan file or duplicate the sketch elsewhere unless the partner explicitly asks.
Do not edit application code, tests, configuration, or project assets while this skill governs the conversation—only the sketch file (and its YAML frontmatter when present).