Skip to content

feat(integration): publish each orchestrator step as one skill - #537

Draft
edwinyjlim wants to merge 1 commit into
dag/m1-delete-promptsfrom
dag/m2-delete-old-step-skills
Draft

edwinyjlim wants to merge 1 commit into
dag/m1-delete-promptsfrom
dag/m2-delete-old-step-skills

Conversation

@edwinyjlim

Copy link
Copy Markdown
Member

What this does

A step of the orchestrator flow is one skill, written once: integration-<step>.

After this change a release has:

  • the 14 step skills, integration-install, integration-init and the rest, unchanged
  • the 40 framework packs, integration-<variant>, unchanged
  • no integration-v2-* skill: 48 zips and 4 group JSON files are gone
  • no replay-vision-enable-replay.json
  • no replaces on a menu entry

How the sources are laid out:

  • Each step skill keeps its template in its own folder, context/skills/integration/<step>/description.md. The 14 templates moved there from context/skills/integration-v2/<step>/ and context/skills/replay-vision-enable-replay/, and each config's template is description.md.
  • context/skills/integration-v2/ and context/skills/replay-vision-enable-replay/ are gone.
  • framework_references is validated on its own. scripts/check-repackaged-skills.js, its package script and its CI step are gone, with compareSkills. composeStepSkill stays as the reference for completing a step skill from a pack.

One skill's text changes

context/skills/replay-vision/description.md, published as replay-vision-setup, tells its agent to install three step skills by name. It now names the ones that publish:

Was Is
replay-vision-enable-replay integration-session-replay
integration-v2-install integration-install
integration-v2-init integration-init

Those 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.
  • The build passes.
  • A build of this branch was compared with a build of the branch below it, both from a clean checkout:
    • 53 files are gone: 48 integration-v2-*.zip, 4 integration-v2-*.json and replay-vision-enable-replay.json.
    • The 14 integration-<step>.zip hold the same files with the same bytes.
    • skill-menu.json goes from 307 entries to 254. The 14 step entries are the same but for replaces, and no other entry differs. cliEntries loses the 248 internal entries of the removed skills.
    • manifest.json and skills-mcp-resources.zip lose the 48 removed skills, and the archive loses the 5 group JSON files.
    • replay-vision-setup.zip differs in the three lines of its SKILL.md above.
    • The marketplace tree is unchanged.

Rollout

Stacked on the prompt removal.

A wizard whose prompts name integration-v2-* or replay-vision-enable-replay finds 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 the integration-<step> skills. Merge it only when all of these hold:

  • cloud runs a wizard release whose prompts name the integration-<step> skills
  • older wizard versions have drained from the run data
  • wizard-agent-dag and wizard-agent-dag-skills are both still on
  • the marketplace and MCP server owners have agreed. The MCP server's archive carries the 48 removed skills today

🤖 Generated with Claude Code

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>
@edwinyjlim
edwinyjlim added this pull request to stack #539 November 17, 2026 01:10
@github-actions

Copy link
Copy Markdown

🧙 Wizard CI

Run 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:

  • /wizard-ci all

Test all apps in a directory:

  • /wizard-ci ai-observability
  • /wizard-ci basic-integration
  • /wizard-ci feature-flags
  • /wizard-ci mcp-analytics
  • /wizard-ci replay-vision
  • /wizard-ci revenue
  • /wizard-ci self-driving
  • /wizard-ci warehouse
  • /wizard-ci warehouse-seeded

Test an individual app:

  • /wizard-ci ai-observability/anthropic
  • /wizard-ci ai-observability/google-adk
  • /wizard-ci ai-observability/groq
Show more apps
  • /wizard-ci ai-observability/manual-capture
  • /wizard-ci ai-observability/openai
  • /wizard-ci ai-observability/openai-agents
  • /wizard-ci ai-observability/opentelemetry
  • /wizard-ci ai-observability/vercel-ai
  • /wizard-ci basic-integration/android
  • /wizard-ci basic-integration/angular
  • /wizard-ci basic-integration/astro
  • /wizard-ci basic-integration/django
  • /wizard-ci basic-integration/fastapi
  • /wizard-ci basic-integration/flask
  • /wizard-ci basic-integration/flutter
  • /wizard-ci basic-integration/javascript-node
  • /wizard-ci basic-integration/javascript-web
  • /wizard-ci basic-integration/laravel
  • /wizard-ci basic-integration/next-js
  • /wizard-ci basic-integration/nuxt
  • /wizard-ci basic-integration/python
  • /wizard-ci basic-integration/rails
  • /wizard-ci basic-integration/react-native
  • /wizard-ci basic-integration/react-router
  • /wizard-ci basic-integration/sveltekit
  • /wizard-ci basic-integration/swift
  • /wizard-ci basic-integration/tanstack-router
  • /wizard-ci basic-integration/tanstack-start
  • /wizard-ci basic-integration/vue
  • /wizard-ci feature-flags/django
  • /wizard-ci feature-flags/next-js
  • /wizard-ci mcp-analytics/custom-dispatcher
  • /wizard-ci mcp-analytics/go-sdk
  • /wizard-ci mcp-analytics/python-sdk
  • /wizard-ci mcp-analytics/ruby-sdk
  • /wizard-ci mcp-analytics/rust-sdk
  • /wizard-ci mcp-analytics/typescript-sdk
  • /wizard-ci replay-vision/javascript-node
  • /wizard-ci replay-vision/next-js
  • /wizard-ci replay-vision/react-vite
  • /wizard-ci revenue/stripe
  • /wizard-ci self-driving/astro
  • /wizard-ci self-driving/fastapi
  • /wizard-ci self-driving/nuxt
  • /wizard-ci self-driving/react-router
  • /wizard-ci self-driving/sveltekit
  • /wizard-ci warehouse/monorepo-env
  • /wizard-ci warehouse/multi-source-next
  • /wizard-ci warehouse/stripe-node
  • /wizard-ci warehouse/zero-source
  • /wizard-ci warehouse-seeded/next-stripe
  • /wizard-ci warehouse-seeded/next-stripe-declined

Test against a wizard branch:

  • /wizard-ci all wizard:my-branch

Add wizard:<branch> to any command above to pin the wizard branch. It defaults to main.

Results will be posted here when complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant