Plugin 9.0: your framework files move to framework/
Plugin 9.0 moves each workflow’s framework record out of outputs/<workflow>/ and into framework/<workflow>/. The requirements, test inputs, design spec, test results, run guide, run log, and improvement plan all live there now, and the opportunity report is framework/ai-opportunity-report.md. The reason is simple: outputs/ is often ignored by version control and buried under everything your workflows produce, so the records you most want to keep were the easiest to lose.
How your workspace is organised now
Section titled “How your workspace is organised now”registry/is the catalog: one card per workflow.framework/<workflow>/is each workflow’s record: requirements,inputs/,context/(any example you pasted in during Deconstruct), design spec, stagedskills/andagents/, test results, run guide, run log, and improvement plan.- Your workflow’s own output, the report or email it produces, lands wherever the workflow runs. It never goes into
framework/.
Where Build can install your skill or agent directly, it installs it where your platform expects it and links to the installed file instead of copying it into framework/. Where it can’t install directly, it keeps a ready-to-upload copy in framework/<workflow>/skills/ for you to upload.
If you already have a workspace
Section titled “If you already have a workspace”You don’t have to move anything yourself. The first time a framework step finds files in outputs/, your assistant lists what will move to framework/ and what stays where it is, then asks once for the whole workspace. Say yes and it moves only the framework files. Say no and everything keeps working; the registry check shows a gentle warning until you are ready.
If you installed a workflow before 9.0
Section titled “If you installed a workflow before 9.0”A workflow you built and installed earlier may point at the old outputs/ paths. If you installed your workflow by uploading a package (anywhere Build gave you a file to upload), you will need to upload it again after its paths are updated. Your assistant walks you through it step by step.
One thing to check: if a skill you built earlier saves its output into framework/, change it to save somewhere else. framework/ is for the workflow’s record, not for what the workflow makes.
If you made your registry from the template repository
Section titled “If you made your registry from the template repository”If you created your registry by clicking Use this template on the AI Registry template, your copy still has the old registry checks. To get the new ones, copy two things from the template into your repository, replacing the old copies: the tools/ folder and the .github/workflows/registry.yml file. Keep your own registry/SCHEMA.md as it is. Your assistant can do this for you if you ask.
The new registry.yml only checks your registry; it no longer publishes a GitHub Pages site. If you turned Pages on earlier, your published dashboard stops updating but stays online: turn it off under Settings → Pages, and consider making the repository Private (Settings → General → Danger Zone → Change visibility). To share your dashboard on Claude, save it as an Artifact instead.
One more change: test data
Section titled “One more change: test data”When Deconstruct asks for test inputs and example outputs, it now asks for inputs like your real work, with names and details made up. Don’t paste client names, personal details, or anything confidential. If you are not sure what to write, ask the assistant to draft a realistic stand-in. A past output with its details changed still works as a golden example.
Update from the plugin marketplace, or download the skill ZIPs. The step pages, such as Deconstruct and Test, show the new paths.