Inspect, then create an implementation brief before mutation: requested assets, supplied references, missing references, scene constraints, camera route, animation beats, duration, and required exports. If a required reference is missing, ask the user for it by default. Create a Blender-designed proxy only when the user explicitly requests design of the missing asset, and record its assumptions and deviations in the delivery receipt.
For an auto_with_budget request, execute the approved brief through every safe milestone
without asking after each preview. Capture the same previews and validation evidence, but present
them together with the final artifact inventory. Stop only for a forbidden missing asset, path
escape, deletion/overwrite, expert Python or failed validation requiring recovery. Remote budget
enforcement is owned by the downstream plugin.
Translate the approved brief into named components, then complete Scene Structure, Modeling,
Materials, Lighting and Camera, Animation, and Final Preview milestones. Use one transaction per
milestone and expectedSceneRevision on every mutation.
Delegate each milestone to the precise domain Skill advertised by capability.describe; do not
keep advanced animation, cinematography, quality validation, background jobs, or simulation under
this general workflow. Multi-domain recipes may load multiple Skills declared by the capability.
Prefer registered commands over expert Python. Read session.status and show the actual scene
in the foreground before work. Update session.set_progress with an honest stage and optional
progress fraction; report actual objects changed, not a synthetic completion percentage.
After each milestone generate fresh previews. In interactive mode wait for approval; in automatic
mode assess the previews against the approved brief, then commit without another prompt.
On failure recover the transaction only if the user has not taken over. Command success alone is not
design acceptance. Before final export, verify all brief constraints that are observable in the
scene and preview: object count and uniqueness, animation beat order, frame range, camera route,
and required deliverable formats. Return the artifact inventory and explicitly ask whether the
user wants to finish locally or hand off only when that choice was not already made.
Downstream AI rendering is outside this Skill.
For foreground control and recovery, hand off to the blender-use skill when the plugin provides
it. Install: npx skills add full-aigc-skills/blender-skills --skill blender-use. If that optional
skill is not published in the current package, follow the session boundary below without inventing
a local file dependency. On SESSION_PAUSED, stop design commands. Only a user resume permits
continuation; then inspect again and begin a new transaction. Never roll back the pre-takeover
transaction over user edits.
When to Use
Use when the user gives a multi-stage Blender finished-product goal and needs modeling, materials, lighting, camera, animation, and delivery coordinated. A single-domain task should directly trigger the corresponding skill.
Prerequisites
- Record the goal, reference assets, prohibited items, scene constraints, camera path, action beats, and delivery format.
- If key assets or acceptance criteria are missing, clarify first; confirm automatic mode, budget, and output root directory.
Workflow
Step 1. Perform a read-only inspection of the scene and capabilities to form an acceptable implementation brief. Step 2. Execute the scene structure, modeling, materials, lighting and camera, animation, and final preview milestones in sequence. Step 3. Transact each milestone separately, use the expected revision number, and hand it to the precise domain skill. Step 4. Generate new previews and measurement evidence; in interactive mode wait for confirmation, in automatic mode self-check against the approved brief. Step 5. Before export, review all observable constraints and return the real artifact list and unfinished items.
Validation and Delivery Evidence (Validation)
Bind each milestone's transaction, scene revision, snapshot, object changes, preview hash, and domain acceptance result. Command success cannot replace design acceptance.
Rules and Capability Boundaries (Not Applicable Scenarios)
This skill is only responsible for orchestration, and does not absorb advanced animation, simulation, background jobs, or external AI rendering capabilities; it does not download assets, publish, or pay on its own.
Gotchas (Common Issues and Recovery)
- User takeover: pause immediately, re-check after recovery, and start a new transaction.
- Revision conflict: stop writing, read the latest scene, and do not overwrite user changes.
- Acceptance failure: return to the corresponding milestone and domain skill, and do not use the final preview to mask defects.