Discovers user intent and generates a structured, step-by-step plan for model customization workflows. This skill must always be activated alongside any other skill when the user's request relates to model customization — including fine-tuning, training, building, customizing, reviewing data, or getting advice on approach, regardless of domain. Do not skip this skill even if the immediate ask is narrow (e.g., reviewing data format or a single workflow step), because planning discovers the full s
SkillScore77Maintained
Automatic
◆AI Engineer pack
Last verified 8/16/2026
What it changes
Passed 17 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill77%
Checks it passed that the model alone missed
The response updates the task status to completed ✅
The response asks what the user would like to do next
The response does not present a numbered list of plan tasks
and 21 more in the full report
14 fixed3 passed either way2 still failing3 broke
Pass-rate lift
+50 pp
Tokens
+41%
Agent turns
0%
Response time
-42%
Model gemini-3.6-flashMeasured 8/16/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
Task 1 'Fine-tune model' finished successfully and generated `scripts/01_sft.py` and `manifests/sft_run.json`. Update the plan file to show completion and outputs.
What was checked, without and with the skill
Checked
Without skill
With skill
The response updates the task status to completed ✅
Missed
Passed
The response records the output file paths under the completed task item in PLAN.md
Missed
Passed
case-11 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md135 lines5 files
Principles
One question at a time. Each question should resolve a branching decision in the plan. Avoid generic or out-of-domain questions.
Surface constraints early. If a user decision would constrain downstream options, flag it before the plan is finalized.
Keep plans short. Only include tasks that are necessary for the user's stated goal.
Don't ask what you already know. Check conversation history and project files before asking the user.
Phase 1: Brainstorming
Goal: Understand what the user wants to accomplish and identify which skills belong in the plan.
Read references/input-output-contracts.md, references/model-customization-plan.md, and references/evaluate-first-plan.md to:
Identify which skills could be relevant to the user's stated goal.
Check whether the user has the necessary input artifacts for each skill. If not, find the skills that generate those inputs and add them first.
Order skills to allow a smooth transition from one to the next and avoid dead ends.
Check if a recommended workflow matches the user's needs. If not, assess what modifications are needed and verify they are possible against the contracts table.
Decide which skills in a matching workflow can be skipped.
Surface limitations early — if a user decision (model choice, region, evaluation method) would constrain downstream options, mention it proactively, get user feedback, and adapt the plan accordingly.
During brainstorming:
Workflow choice gate: Before generating any plan, determine whether the user wants the evaluate-first workflow or the direct fine-tuning workflow. If the user has explicitly chosen (e.g., "evaluate first", "skip evaluation", "already evaluated the base model"), proceed with their choice. Otherwise, present both options with brief pros/cons and ask the user to choose. Saying "fine-tune" or naming a technique alone is NOT an explicit choice to skip evaluation — the user may not know evaluate-first is an option. Do NOT present a plan until the user has chosen a path. After they choose, read ONLY the corresponding reference plan.
Use the Restrictions column of the contracts table to flag constraints as soon as the relevant decision is made. Examples (non-comprehensive list, check contracts table for the full picture):
User picks a Nova model → alert that deployment regions are limited.
User picks a region → alert if it conflicts with model availability.
If a restriction applies, check whether it requires changes to other steps in the plan.
Do NOT ask the user about base model selection or preferences. Model selection is handled exclusively by the model-selection skill.
Move to Phase 2 as soon as you can determine which skills and tools the plan needs.
Phase 2: Plan Generation
Goal: Propose a structured plan for the user to review.
Generate a plan as a numbered list of tasks. Each task has: