Name: csharp-modernization-kickoff-from-github
Author: Mayank1619

Prompt file imported from Mayank1619/C-ModernizingAgenticFramework (.github/prompts/csharp-modernization-kickoff-from-github.prompt.md). Copyright stays with the author.

Use the CSharp Modernization Orchestrator.

Inputs:

LEGACY_REPO_URL (required unless LEGACY_ROOT is provided): GitHub repository URL for legacy code.
LEGACY_REPO_REF (optional): branch/tag/commit. Default: repository default branch.
LEGACY_SUBPATH (optional): subfolder inside repo containing legacy code.
UPLIFT_ROOT (optional): target code root in current workspace. Default: UpliftedCode if present, otherwise current repo root.
ARTIFACT_FOLDER (required): output artifact folder.
SOURCE_SCOPE and TARGET_SCOPE (optional): bounded context scopes; default to resolved legacy and uplift roots.

Interactive kickoff behavior:

If LEGACY_REPO_URL is missing and no local LEGACY_ROOT is confirmed, ask the user for the GitHub URL first and wait.
Echo resolved inputs and ask for explicit approval before cloning.
After cloning/path resolution, ask for explicit approval before artifact generation.
After artifact generation and gate checks, ask for explicit approval before declaring kickoff complete.
For every pause, require one of: APPROVE, REJECT, NEEDS_CHANGES.
For human gates, collect reviewer details in chat and auto-write gate files before running validation scripts.

Execution workflow:

Clone the legacy repo into .external/legacy-source in the current workspace.
If LEGACY_SUBPATH is provided, set LEGACY_ROOT=.external/legacy-source/<LEGACY_SUBPATH>; otherwise use .external/legacy-source.
Resolve UPLIFT_ROOT and confirm both roots exist.
Build and validate bounded repository context after cloning and path resolution.
Do not invoke legacy analysis until context status is VALID.
Run kickoff artifact generation (analysis, business rules, requirements, spec, tasks, traceability, manifest) and declare the context manifest for new runs.
Run human-gate template initialization.
Run gate validations when scripts are available.
Do not implement code in kickoff.

Mandatory output:

Resolved paths: LEGACY_ROOT, UPLIFT_ROOT, ARTIFACT_FOLDER.
Clone command/result summary.
Gate command/result summary (or SCRIPT_NOT_FOUND).
Readiness decision and next required human action.

Use the CSharp Modernization Orchestrator. Inputs: - `LEGACY_REPO_URL` (required unless `LEGACY_ROOT` is provided): GitHub repository URL for legacy code. - `LEGACY_REPO_REF` (optional): branch/tag/commit. Default: repository default branch. - `LEGACY_SUBPATH` (optional): subfolder inside repo containing legacy code. - `UPLIFT_ROOT` (optional): target code root in current workspace. Default: `UpliftedCode` if present, otherwise current repo root. - `ARTIFACT_FOLDER` (required): output artifact folder. - `SOURCE_SCOPE` and `TARGET_SCOPE` (optional): bounded context scopes; default to resolved legacy and uplift roots. Interactive kickoff behavior: 1. If `LEGACY_REPO_URL` is missing and no local `LEGACY_ROOT` is confirmed, ask the user for the GitHub URL first and wait. 2. Echo resolved inputs and ask for explicit approval before cloning. 3. After cloning/path resolution, ask for explicit approval before artifact generation. 4. After artifact generation and gate checks, ask for explicit approval before declaring kickoff complete. 5. For every pause, require one of: APPROVE, REJECT, NEEDS_CHANGES. 6. For human gates, collect reviewer details in chat and auto-write gate files before running validation scripts. Execution workflow: 1. Clone the legacy repo into `.external/legacy-source` in the current workspace. 2. If `LEGACY_SUBPATH` is provided, set `LEGACY_ROOT=.external/legacy-source/<LEGACY_SUBPATH>`; otherwise use `.external/legacy-source`. 3. Resolve `UPLIFT_ROOT` and confirm both roots exist. 4. Build and validate bounded repository context after cloning and path resolution. 5. Do not invoke legacy analysis until context status is `VALID`. 6. Run kickoff artifact generation (analysis, business rules, requirements, spec, tasks, traceability, manifest) and declare the context manifest for new runs. 7. Run human-gate template initialization. 8. Run gate validations when scripts are available. 9. Do not implement code in kickoff. Mandatory output: - Resolved paths: `LEGACY_ROOT`, `UPLIFT_ROOT`, `ARTIFACT_FOLDER`. - Clone command/result summary. - Gate command/result summary (or `SCRIPT_NOT_FOUND`). - Readiness decision and next required human action.

{ "prompt": "Use the CSharp Modernization Orchestrator.\n\nInputs:\n- `LEGACY_REPO_URL` (required unless `LEGACY_ROOT` is provided): GitHub repository URL for legacy code.\n- `LEGACY_REPO_REF` (optional): branch/tag/commit. Default: repository default branch.\n- `LEGACY_SUBPATH` (optional): subfolder inside repo containing legacy code.\n- `UPLIFT_ROOT` (optional): target code root in current workspace. Default: `UpliftedCode` if present, otherwise current repo root.\n- `ARTIFACT_FOLDER` (required): output artifact folder.\n- `SOURCE_SCOPE` and `TARGET_SCOPE` (optional): bounded context scopes; default to resolved legacy and uplift roots.\n\nInteractive kickoff behavior:\n1. If `LEGACY_REPO_URL` is missing and no local `LEGACY_ROOT` is confirmed, ask the user for the GitHub URL first and wait.\n2. Echo resolved inputs and ask for explicit approval before cloning.\n3. After cloning/path resolution, ask for explicit approval before artifact generation.\n4. After artifact generation and gate checks, ask for explicit approval before declaring kickoff complete.\n5. For every pause, require one of: APPROVE, REJECT, NEEDS_CHANGES.\n6. For human gates, collect reviewer details in chat and auto-write gate files before running validation scripts.\n\nExecution workflow:\n1. Clone the legacy repo into `.external/legacy-source` in the current workspace.\n2. If `LEGACY_SUBPATH` is provided, set `LEGACY_ROOT=.external/legacy-source/<LEGACY_SUBPATH>`; otherwise use `.external/legacy-source`.\n3. Resolve `UPLIFT_ROOT` and confirm both roots exist.\n4. Build and validate bounded repository context after cloning and path resolution.\n5. Do not invoke legacy analysis until context status is `VALID`.\n6. Run kickoff artifact generation (analysis, business rules, requirements, spec, tasks, traceability, manifest) and declare the context manifest for new runs.\n7. Run human-gate template initialization.\n8. Run gate validations when scripts are available.\n9. Do not implement code in kickoff.\n\nMandatory output:\n- Resolved paths: `LEGACY_ROOT`, `UPLIFT_ROOT`, `ARTIFACT_FOLDER`.\n- Clone command/result summary.\n- Gate command/result summary (or `SCRIPT_NOT_FOUND`).\n- Readiness decision and next required human action.", "variables": [], "notes": "Bootstrap modernization by cloning legacy source from a GitHub repo into current workspace, then run kickoff artifacts and gates. Mode: agent.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/Mayank1619/C-ModernizingAgenticFramework", "path": ".github/prompts/csharp-modernization-kickoff-from-github.prompt.md", "ref": "bf3ca042e617774fb7d7b68cdc51c4f687739f8a", "url": "https://github.com/Mayank1619/C-ModernizingAgenticFramework/blob/bf3ca042e617774fb7d7b68cdc51c4f687739f8a/.github/prompts/csharp-modernization-kickoff-from-github.prompt.md", "key": "Mayank1619/C-ModernizingAgenticFramework/.github/prompts/csharp-modernization-kickoff-from-github.prompt.md" } }, "model_hints": [ "GPT-5" ] }

csharp-modernization-kickoff-from-github

About

Use it

Manifest

Reviews