MSW BehaviourTree Creator

Authors .behaviourtree files. The project's discovered node catalog lives in .behaviourDocs/bt-spec.md; fixed graph rules and skeletons live in this skill's references/ folder.

🚦 Execution order (follow this sequence)

0. Locate / refresh the project spec

• Read <ProjectRoot>/.behaviourDocs/bt-spec.md. It is the source of truth for project-specific data: every custom action / decorator node's definitionId, btNodeType, visible propertyKey names, and the serialized Type.type strings stamped to this project's CoreVersion.
• The compact spec intentionally lists only property names. When constructing nodeProperties, resolve each property's mlua type/default from the paired .mlua file, then use the type map in bt-spec.md §4 for propertyType.type.
• If the file is missing, stop and invoke msw-behaviourtree-spec-builder first. If running manually, execute that skill's local scripts/build-spec.cjs with --projectRoot set to the MSW project root.
• If the user says they recently added/changed a BT codeblock or a .mlua property, refresh the spec (re-run the builder skill) before proceeding — stale UUIDs / missing properties silently produce broken trees.
• Also read references/skeleton-minimal.json for the smallest valid tree, references/skeleton-full.json for a Composite+Decorator+Action+Blackboard example with all optional fields populated, references/node-catalog.md for fixed graph rules, and any existing .behaviourtree in the project (**/*.behaviourtree) to mirror conventions. Replace {CORE_VERSION} in the skeletons with the CoreVersion from bt-spec.md — both at the top level and inside every MOD.Core.* type string in Blackboard variables and nodeProperties.

1. Collect input from the user

Confirm via context, or ask via AskUserQuestion if anything is ambiguous: