← WidemileCONTENT HISTORY
WHAT CHANGED
Update to Widemile
Snapshot Oct 24, 2026 · 13:07 UTC · version 1.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Widemile and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Read and revise the canonical free-form ProStudio Markdown Brief while keeping technical workflow state separate.",
"included_files": [],
"name": "production-planning",
"skill_md_contents": "---\nname: production-planning\ndescription: Read and revise the canonical free-form ProStudio Markdown Brief while keeping technical workflow state separate.\n---\n\n# Production planning\n\n## Tool requirements\n\n- **Core:** `prostudio_brief_get` and `prostudio_brief_replace`.\n- **Conditional operational context:** `prostudio_references_list` and `prostudio_references_resolve` when exact reference bindings must be identified; `prostudio_shot_generation_set` only when the user requests an operational assignment outside the Brief.\n- This declaration does not activate tools. Use only the tools required by the selected branch. If a required tool is absent from the current scoped catalog and `load_prostudio_tools` is available, call it with the missing outcome before claiming the capability is unavailable; do not call it when the tool is already available. If retrieval still exposes no matching tool, report that limitation.\n\n- Treat \"brief\", \"draft\", \"bozza\", and \"piano\" as one free-form Markdown document containing human creative context only.\n- Read `prostudio_brief_get` whenever a request depends on current context. To revise it, preserve unrelated prose and call `prostudio_brief_replace` with the complete Markdown plus the current `briefRevision` as `expectedRevision`.\n- The Brief has no required headings or machine schema. Never put model ids, reference ids, generation ids, job status, credit state, or workflow state in it.\n- Generation plans are independent immutable technical snapshots. Select model options and explicit reference bindings when preparing each generation; Brief edits do not invalidate prepared plans.\n- Completed generations and optional workflow-step assignments live outside the Brief. Use `prostudio_shot_generation_set` only for that operational assignment.\n- References live outside the Brief. Read the library and pass exact reference ids explicitly to the generation workflow; never infer or synchronize bindings by parsing Markdown.\n"
}SHA-256 of public snapshot: 099936eb1d9f49d529d7ef78c28b4d67337e693cdcd2a61fd755b87fc8867a87