Repository navigation
feat(integration): publish each orchestrator step as one skill - #537
Draft
edwinyjlim wants to merge 1 commit into
Draft
edwinyjlim wants to merge 1 commit into
edwinyjlim wants to merge 1 commit into
Conversation
A step of the orchestrator flow is one skill, `integration-<step>`, with its template in its own folder under `context/skills/integration/`. The per-framework step skills under `integration-v2` and `replay-vision-enable-replay` are no longer built, and a menu entry carries no `replaces`. The Replay vision skill names the step skills it hands its agent to. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a wizard branch:
Add Results will be posted here when complete. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
A step of the orchestrator flow is one skill, written once:
integration-<step>.After this change a release has:
integration-install,integration-initand the rest, unchangedintegration-<variant>, unchangedintegration-v2-*skill: 48 zips and 4 group JSON files are gonereplay-vision-enable-replay.jsonreplaceson a menu entryHow the sources are laid out:
context/skills/integration/<step>/description.md. The 14 templates moved there fromcontext/skills/integration-v2/<step>/andcontext/skills/replay-vision-enable-replay/, and each config'stemplateisdescription.md.context/skills/integration-v2/andcontext/skills/replay-vision-enable-replay/are gone.framework_referencesis validated on its own.scripts/check-repackaged-skills.js, its package script and its CI step are gone, withcompareSkills.composeStepSkillstays as the reference for completing a step skill from a pack.One skill's text changes
context/skills/replay-vision/description.md, published asreplay-vision-setup, tells its agent to install three step skills by name. It now names the ones that publish:replay-vision-enable-replayintegration-session-replayintegration-v2-installintegration-installintegration-v2-initintegration-initThose three are written once for every framework, with placeholders for the framework's name, pages and rules. A consumer that installs one outside the orchestrator has to complete it from the framework's pack the same way.
Verification
npm test: 391 tests pass.integration-v2-*.zip, 4integration-v2-*.jsonandreplay-vision-enable-replay.json.integration-<step>.ziphold the same files with the same bytes.skill-menu.jsongoes from 307 entries to 254. The 14 step entries are the same but forreplaces, and no other entry differs.cliEntriesloses the 248internalentries of the removed skills.manifest.jsonandskills-mcp-resources.ziplose the 48 removed skills, and the archive loses the 5 group JSON files.replay-vision-setup.zipdiffers in the three lines of itsSKILL.mdabove.Rollout
Stacked on the prompt removal.
A wizard whose prompts name
integration-v2-*orreplay-vision-enable-replayfinds no skill under those names once this ships, and its run fails at preflight. That is every wizard release before the one whose prompts name theintegration-<step>skills. Merge it only when all of these hold:integration-<step>skillswizard-agent-dagandwizard-agent-dag-skillsare both still on🤖 Generated with Claude Code