Skip to content

Add Workflows to Squads migration guide#1081

Open
bets-margulies-vapi wants to merge 2 commits into
mainfrom
claude/gracious-rubin-mzli9i
Open

Add Workflows to Squads migration guide#1081
bets-margulies-vapi wants to merge 2 commits into
mainfrom
claude/gracious-rubin-mzli9i

Conversation

@bets-margulies-vapi

Copy link
Copy Markdown
Contributor

Description

  • Added comprehensive migration guide (workflows/legacy-migration.mdx) for transitioning from Workflows to Squads before the August 18, 2026 deprecation deadline
  • Guide includes:
    • Deprecation timeline and rationale for the product shift
    • Concept mapping table showing how Workflows components translate to Squads
    • Assisted migration path using Composer for auto-drafting equivalent Squads
    • Step-by-step manual migration instructions (6 steps from mapping to testing)
    • Variable extraction and handoff tool configuration guidance
    • Comprehensive FAQ addressing common migration questions
    • Links to related Squads documentation and examples
  • Updated docs.yml navigation to surface the migration guide prominently under Workflows section

Testing Steps

  • Run fern docs dev and verify the migration guide renders correctly
  • Confirm the new page appears in the Workflows navigation section
  • Verify all internal links (to /squads, /squads/handoff, etc.) resolve properly
  • Check that the warning banner and note callouts display correctly
  • Validate the concept mapping table and code example format

https://claude.ai/code/session_01KfSaT4cFb2DggCYTctrzEq

Add a legacy migration guide at /workflows/legacy-migration covering the
Workflows retirement (August 18, 2026), concept mapping to Squads, the
Composer-assisted path, step-by-step manual migration, and FAQs. Link it
from the Workflows nav section.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KfSaT4cFb2DggCYTctrzEq
@bets-margulies-vapi bets-margulies-vapi self-assigned this Jun 24, 2026
@github-actions

Copy link
Copy Markdown
Contributor

- Step 5: use memberOverrides for squad-wide settings (e.g. same voice);
  assistantOverrides is per-member. Add a memberOverrides example.
- Step 2: recommend bundling as much as possible into one assistant and
  consolidating stages with cyclical handoffs, since Squads work best for
  linear, unidirectional flows.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KfSaT4cFb2DggCYTctrzEq

Copy link
Copy Markdown
Contributor Author

Addressed the review feedback:

  • Step 5 now uses memberOverrides for squad-wide settings (the API docs were correct — assistantOverrides is per-member).
  • Step 2 now recommends bundling as much as possible into one assistant and consolidating stages with cyclical handoffs.

Generated by Claude Code

@github-actions

Copy link
Copy Markdown
Contributor

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.

2 participants