Dynamic Workflow Migration Planner Agent
Community reusable agent prompt for migrating teams to Claude Code dynamic workflows using official workflows documentation: audit phases, YAML or config migration steps, validation gates, and rollback planning for large codebase automation.
Open the source and read safety notes before installing.
Safety notes
- Automated workflows can run destructive tools without mid-flight prompts—scope permissions narrowly.
- Pilot migrations on non-production repositories before enabling org-wide schedules.
- Rollback plans must include disabling workflow triggers and revoking connector access.
- Do not migrate production deploy steps until validation gates pass in staging.
Privacy notes
- Workflow definitions may embed internal service names, ticket templates, or customer examples.
- Migration audits can expose legacy prompts with secrets—scrub before archiving in git.
- Shared workflow repos inherit normal code review and access control requirements.
Prerequisites
- Inventory of existing slash commands, hooks, or manual Claude playbooks to migrate.
- Access to repositories where dynamic workflows will be committed.
- Team agreement on validation gates, human approvals, and rollback triggers.
- Pilot repository for testing migrated workflows before org-wide rollout.
Schema details
- Install type
- copy
- Troubleshooting
- No
- Scope
- Source repo
Full copyable content
## Content
Dynamic Workflow Migration Planner Agent is a community-authored reusable prompt for
planning migration to Claude Code dynamic workflows. It applies official workflows
documentation—not an official Anthropic migration service.
## Scope Note
This prompt operationalizes documented workflow capabilities from code.claude.com.
Execution and merge authority remain with your team.
## Agent Prompt
You are a dynamic workflow migration planner for Claude Code. Convert ad-hoc automation
into documented workflows using official workflows guidance.
Workflow:
1. **Inventory legacy automation.** List slash commands, hooks, scripts, and manual runbooks.
2. **Map to workflow phases.** Align each legacy step to workflow nodes with validation gates.
3. **Scope repositories.** Limit workflow repos, connectors, and permissions per least privilege.
4. **Pilot plan.** Choose a pilot repo, success metrics, and rollback triggers.
5. **Validation design.** Define deterministic checks (tests, lint) between AI phases.
6. **Rollout waves.** Sequence team adoption with training and support windows.
7. **Rollback.** Document how to disable workflows and restore legacy playbooks.
Output contract:
- Legacy-to-workflow mapping table.
- Pilot migration checklist with owners.
- Validation gate definitions.
- Rollout timeline and rollback runbook.
## Features
- Applies official workflows docs to migration planning.
- Separates AI phases from deterministic validation nodes.
- Emphasizes pilot repos and rollback before org-wide enablement.
- Produces engineering-ready migration backlogs.
## Use Cases
- Migrate manual audit playbooks to dynamic workflows for large monorepos.
- Standardize release hygiene workflows across business units.
- Plan connector scope before enabling scheduled workflow runs.
- Document rollback before enabling autonomous maintenance workflows.
## Source Notes
Verified against Claude Code workflows documentation on **2026-06-16**:
- Official docs describe dynamic workflows for structuring multi-phase Claude Code
automation with explicit steps and validation patterns.
- Documentation supports combining AI-driven phases with deterministic checks suitable
for large codebase audits and maintenance tasks.
- Workflows integrate with repository context, permissions, and connector settings
documented elsewhere in Claude Code guides.
## Duplicate Check
Checked content/agents and content/guides for workflow migration coverage.
dynamic-workflows-for-large-codebase-audits is a guides entry for audit workflows.
No agents entry provides migration planning from legacy automation to dynamic workflows
with pilot and rollback contracts grounded in official workflows docs.
## Editorial Disclosure
Submitted as an independent community agent entry by kiannidev, based on public Claude
Code workflows documentation and the public anthropics/claude-code repository.
No paid placement, referral, or affiliate relationship.
## Sources
- Claude Code workflows - https://code.claude.com/docs/en/workflows
- Dynamic workflows for large codebase audits guide - content/guides/dynamic-workflows-for-large-codebase-audits.mdx
- Claude Code repository - https://github.com/anthropics/claude-codeAbout this resource
Content
Dynamic Workflow Migration Planner Agent is a community-authored reusable prompt for planning migration to Claude Code dynamic workflows. It applies official workflows documentation—not an official Anthropic migration service.
Scope Note
This prompt operationalizes documented workflow capabilities from code.claude.com. Execution and merge authority remain with your team.
Agent Prompt
You are a dynamic workflow migration planner for Claude Code. Convert ad-hoc automation into documented workflows using official workflows guidance.
Workflow:
- Inventory legacy automation. List slash commands, hooks, scripts, and manual runbooks.
- Map to workflow phases. Align each legacy step to workflow nodes with validation gates.
- Scope repositories. Limit workflow repos, connectors, and permissions per least privilege.
- Pilot plan. Choose a pilot repo, success metrics, and rollback triggers.
- Validation design. Define deterministic checks (tests, lint) between AI phases.
- Rollout waves. Sequence team adoption with training and support windows.
- Rollback. Document how to disable workflows and restore legacy playbooks.
Output contract:
- Legacy-to-workflow mapping table.
- Pilot migration checklist with owners.
- Validation gate definitions.
- Rollout timeline and rollback runbook.
Features
- Applies official workflows docs to migration planning.
- Separates AI phases from deterministic validation nodes.
- Emphasizes pilot repos and rollback before org-wide enablement.
- Produces engineering-ready migration backlogs.
Use Cases
- Migrate manual audit playbooks to dynamic workflows for large monorepos.
- Standardize release hygiene workflows across business units.
- Plan connector scope before enabling scheduled workflow runs.
- Document rollback before enabling autonomous maintenance workflows.
Source Notes
Verified against Claude Code workflows documentation on 2026-06-16:
- Official docs describe dynamic workflows for structuring multi-phase Claude Code automation with explicit steps and validation patterns.
- Documentation supports combining AI-driven phases with deterministic checks suitable for large codebase audits and maintenance tasks.
- Workflows integrate with repository context, permissions, and connector settings documented elsewhere in Claude Code guides.
Duplicate Check
Checked content/agents and content/guides for workflow migration coverage. dynamic-workflows-for-large-codebase-audits is a guides entry for audit workflows. No agents entry provides migration planning from legacy automation to dynamic workflows with pilot and rollback contracts grounded in official workflows docs.
Editorial Disclosure
Submitted as an independent community agent entry by kiannidev, based on public Claude Code workflows documentation and the public anthropics/claude-code repository. No paid placement, referral, or affiliate relationship.
Sources
- Claude Code workflows - https://code.claude.com/docs/en/workflows
- Dynamic workflows for large codebase audits guide - content/guides/dynamic-workflows-for-large-codebase-audits.mdx
- Claude Code repository - https://github.com/anthropics/claude-code
Source citations
Add this badge to your README
Show that Dynamic Workflow Migration Planner Agent is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/agents/dynamic-workflow-migration-planner-agent)How it compares
Dynamic Workflow Migration Planner Agent side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Dynamic Workflow Migration Planner Agent Community reusable agent prompt for migrating teams to Claude Code dynamic workflows using official workflows documentation: audit phases, YAML or config migration steps, validation gates, and rollback planning for large codebase automation. Open dossier | Claude Agent SDK Subagent Orchestration Capability Pack Skill Expert Claude Agent SDK subagent orchestration capability pack for designing, reviewing, and rolling out Agent SDK subagent orchestration with source-backed checklists, production rules, and privacy-safe output contracts. Open dossier | Computer Use GUI Test Agent Community reusable agent prompt for end-to-end GUI validation with Claude Code computer use using official documentation: enable the computer-use MCP server, per-app session approval, screenshot checkpoints, and documented example workflows for native apps. Open dossier | Agent Observability SRE Agent Community reusable agent prompt for Claude Code analytics and agent platform on-call using official analytics documentation: usage signals, session failure triage, MCP latency patterns, and SRE runbooks for agent hosting teams. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | agents | skills | agents | agents |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | kiannidev | kiannidev | kiannidev | kiannidev |
| Added | 2026-06-16 | 2026-06-14 | 2026-06-16 | 2026-06-16 |
| Platforms | Claude Code | Claude CodeCodexWindsurfGeminiCursorCLI | Claude Code | Claude Code |
| Source repo | — | — | — | — |
| Safety notes | ✓Automated workflows can run destructive tools without mid-flight prompts—scope permissions narrowly. Pilot migrations on non-production repositories before enabling org-wide schedules. Rollback plans must include disabling workflow triggers and revoking connector access. Do not migrate production deploy steps until validation gates pass in staging. | ✓This skill plans Agent SDK subagent orchestration; it must not execute destructive changes without explicit approval. Browser, computer-use, and remote surfaces can access sensitive UI state; scope tests carefully. MCP and SDK integrations may exfiltrate data if tool scopes are too broad. The public `anthropics/claude-code` repository ships documentation links to code.claude.com for settings, security, and integration surfaces. Scheduled or autonomous workflows compound risk; cap blast radius in staging first. | ✓Computer use controls real desktop apps with per-app session approval—not sandboxed Bash. Review sentinel warnings before approving Terminal, Finder, or System Settings access. Press Esc or Ctrl+C to stop computer use and release the session lock immediately. Only one Claude Code session can hold the computer-use lock at a time. | ✓Incident commands must not exfiltrate customer prompts into public tickets. Scaling replicas without reviewing tool side effects can amplify destructive MCP calls. Disabling tracing to reduce noise may hide regressions—prefer sampling over full off. Rollback plans should include MCP allowlist and permission settings, not only code. |
| Privacy notes | ✓Workflow definitions may embed internal service names, ticket templates, or customer examples. Migration audits can expose legacy prompts with secrets—scrub before archiving in git. Shared workflow repos inherit normal code review and access control requirements. | ✓Reviews may expose integration tokens, customer metadata, and internal URLs related to Agent SDK subagent orchestration. Telemetry and analytics configs can include account emails; redact before sharing externally. Keep troubleshooting logs in internal channels unless explicitly sanitized. Third-party vendors remain outside Anthropic retention policies; document separately. | ✓Screenshots are downscaled before model upload but may still capture sensitive UI content. Your terminal window is excluded from screenshots per official documentation. Redact customer or proprietary UI details before sharing screenshot evidence externally. | ✓Analytics and logs may contain prompts, diffs, and credentials if misconfigured. Recommend redaction before exporting incident timelines externally. Shared dashboards should aggregate metrics without raw user content fields. |
| Prerequisites |
|
|
|
|
| Install | — | — | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Featured in
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.