# Iteration Directions Skill: `yao-meta-skill` - Maturity tier: `governed` - Selection rule: Pick the three smallest next steps that increase reliability more than they increase context cost. - Start here: `Borrow one proven pattern on purpose` - Why first: You already have public benchmark objects. The next gain is to choose one pattern intentionally instead of absorbing everything loosely. - Defer for now: `Create an iteration evidence loop` ## Top 3 Next Moves ### 2. Borrow one proven pattern on purpose - Why now: You already have public benchmark objects. The next gain is to choose one pattern intentionally instead of absorbing everything loosely. - Timing: Do this first. - Recommended actions: - Read the strongest pattern from obra/superpowers. - Unlocks: A cleaner package shape with less accidental over-design. - Wait on: Wait to add broader structure until this move clearly improves reliability. - Decide whether to borrow method, structure, execution, or portability, but only one of them first. - Unlocks: A cleaner package shape with less accidental over-design. - Wait on: Wait to add broader structure until this move clearly improves reliability. - Record what you will not borrow so the package stays light. - Unlocks: A cleaner package shape with less accidental over-design. - Wait on: Wait to add broader structure until this move clearly improves reliability. ### 5. Harden portability semantics - Why now: The skill already signals reuse across environments, so contract clarity matters early. - Timing: Do this after the first move lands cleanly. - Recommended actions: - Confirm activation mode, execution context, and trust assumptions. - Unlocks: Safer cross-environment reuse with less target drift. - Wait on: Wait until the package has evidence that this extra structure is justified. - Add or review degradation strategy for non-native targets. - Unlocks: Safer cross-environment reuse with less target drift. - Wait on: Wait until the package has evidence that this extra structure is justified. - Package the skill once to verify adapter expectations. - Unlocks: Safer cross-environment reuse with less target drift. - Wait on: Wait until the package has evidence that this extra structure is justified. ### 12. Create an iteration evidence loop - Why now: The package should show what changed and why after the first draft. - Timing: Do this after the first move lands cleanly. - Recommended actions: - Generate the HTML skill report and keep it aligned with the package. - Unlocks: A clearer path for the next author or reviewer. - Wait on: Wait until the package has evidence that this extra structure is justified. - Record reference scan choices and non-goals. - Unlocks: A clearer path for the next author or reviewer. - Wait on: Wait until the package has evidence that this extra structure is justified. - Capture the next iteration choice explicitly before adding more files. - Unlocks: A clearer path for the next author or reviewer. - Wait on: Wait until the package has evidence that this extra structure is justified.