Name: migration.migrate-mvc-feature-by-plan
Author: SaintberLab

Prompt file imported from SaintberLab/Saintber.CopilotLibrary (.github/prompts/migration.migrate-mvc-feature-by-plan.prompt.md). Copyright stays with the author.

Migrate the selected MVC feature using the required plan-first workflow.

Required process:

Review or update /Tasks/architecture-migration-template.md, /Tasks/backend-migration-template.md, and /Tasks/frontend-migration-template.md as needed
Create scope-specific execution plans for architecture, backend, and frontend aspects of the selected feature
Locate the target Controller and related Actions
Identify required dependent files and components
Move or copy required files into the new project structure when needed
Update namespaces to match the new structure
Perform backend migration tasks
Perform frontend migration tasks
Validate build/compile and fix blocking issues

Migration policy:

preserve legacy behavior whenever possible
avoid unnecessary rewrites
only replace unsupported patterns with the closest compatible equivalent
all generated execution plans must comply with the policies defined under /docs/policy/. Review relevant policy documents before finalizing each plan.

Migrate the selected MVC feature using the required plan-first workflow. Required process: 1. Review or update `/Tasks/architecture-migration-template.md`, `/Tasks/backend-migration-template.md`, and `/Tasks/frontend-migration-template.md` as needed 2. Create scope-specific execution plans for architecture, backend, and frontend aspects of the selected feature 3. Locate the target Controller and related Actions 4. Identify required dependent files and components 5. Move or copy required files into the new project structure when needed 6. Update namespaces to match the new structure 7. Perform backend migration tasks 8. Perform frontend migration tasks 9. Validate build/compile and fix blocking issues Migration policy: - preserve legacy behavior whenever possible - avoid unnecessary rewrites - only replace unsupported patterns with the closest compatible equivalent - all generated execution plans must comply with the policies defined under `/docs/policy/`. Review relevant policy documents before finalizing each plan.

{ "prompt": "Migrate the selected MVC feature using the required plan-first workflow.\n\nRequired process:\n1. Review or update `/Tasks/architecture-migration-template.md`, `/Tasks/backend-migration-template.md`, and `/Tasks/frontend-migration-template.md` as needed\n2. Create scope-specific execution plans for architecture, backend, and frontend aspects of the selected feature\n3. Locate the target Controller and related Actions\n4. Identify required dependent files and components\n5. Move or copy required files into the new project structure when needed\n6. Update namespaces to match the new structure\n7. Perform backend migration tasks\n8. Perform frontend migration tasks\n9. Validate build/compile and fix blocking issues\n\nMigration policy:\n- preserve legacy behavior whenever possible\n- avoid unnecessary rewrites\n- only replace unsupported patterns with the closest compatible equivalent\n- all generated execution plans must comply with the policies defined under `/docs/policy/`. Review relevant policy documents before finalizing each plan.", "variables": [], "notes": "Migrate one MVC feature by first preparing plan files, then executing the migration", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/SaintberLab/Saintber.CopilotLibrary", "path": ".github/prompts/migration.migrate-mvc-feature-by-plan.prompt.md", "ref": "30614ec3573097f542066b2bcf9c43e5ce13e09e", "url": "https://github.com/SaintberLab/Saintber.CopilotLibrary/blob/30614ec3573097f542066b2bcf9c43e5ce13e09e/.github/prompts/migration.migrate-mvc-feature-by-plan.prompt.md", "key": "SaintberLab/Saintber.CopilotLibrary/.github/prompts/migration.migrate-mvc-feature-by-plan.prompt.md" } } }

migration.migrate-mvc-feature-by-plan

About

Use it

Manifest

Reviews