Name: timeslice-plan
Author: DeltaE

Prompt file imported from DeltaE/BC_Nexus (.github/prompts/timeslice-plan.prompt.md). Copyright stays with the author.

Create a surgical temporal slicing adjustment plan for the requested workflow.

Use the temporal-slicing-adjustment skill and anchor the analysis in BCNexus when the target workflow is this repository.

If the user's workflow stages are incomplete, unclear, or use unfamiliar naming, ask a small set of targeted clarification questions before producing the plan. In particular, ask about:

where temporal aggregation or representative-day logic currently happens
whether temporal slicing is part of the base workflow or a scenario axis of its own
whether the user wants timeslice adjustment to happen before scenario application, after scenario application, or differently for different scenario families
what stage applies non-temporal scenario changes
whether the scenario mechanism changes storage structure, temporal structure, demand/emissions/technology values, or some combination
whether the workflow has one storage algorithm or multiple storage algorithms
which storage algorithms are present and whether temporal slicing must work across all of them or only selected ones
what representation the model inputs use before export, such as CSVs, tables, dataframes, or .dat fragments
what stage exports the final model input package
what script, tool, or step performs preprocessing after export
whether the workflow is object-oriented, script-based, notebook-driven, or pipeline-based

Use those answers to connect the target workflow back to the BCNexus stage pattern:

temporal shaping
non-temporal scenario overlay
final datafile export
preprocessing handoff

Do not assume the user's scenario mechanism matches BCNexus. If temporal slicing itself is a scenario dimension, plan the entry point around that fact instead of forcing a pre-scenario temporal stage.

If the user already gave enough workflow structure, do not ask extra questions.

Required output:

Clarifications Used

List the workflow-stage details the user provided or confirmed.
State whether temporal slicing is a base-workflow step or a scenario axis.
State whether the workflow has multiple storage algorithms and which ones matter for the plan.
If no clarification was needed, state that the existing context was sufficient.

Workflow Position

State exactly where temporal slicing belongs in the workflow.
State what must happen before it and after it.
State whether that position changes when temporal slicing is treated as a scenario-specific branch.

Control Path

Identify the controlling functions, scripts, stages, or modules.
For BCNexus, trace the path through RunModel, the builder temporal logic, scenario overlay, datafile export, and preprocessing.
For non-BCNexus workflows, explicitly map the user's stage names onto the equivalent BCNexus stages.

Required Changes

List the minimum implementation steps needed.
Separate temporal metadata computation, temporal table rewrites, clustered profile rewrites, scenario overlay, and export/preprocessing handoff.

Storage Scope

State whether the plan covers a single storage algorithm or multiple storage algorithms.
If the workflow uses storage structures beyond Niet or Kotzur, state that the BCNexus-derived guidance is only directly validated for Niet/Kotzur-style storage structures and explain any resulting uncertainty.

Non-OOP Adaptation

If the target workflow is not object-oriented, rewrite the plan as a linear pipeline of functions or scripts.

Validation

Give the narrowest checks that prove the temporal slicing wiring is correct.

Constraints:

Keep the plan specific to the described workflow, not generic boilerplate.
Preserve the ordering required by the user's actual workflow. If temporal slicing is not a scenario axis, default to temporal shaping before non-temporal scenario overlay, and both before final datafile generation and preprocessing.
If temporal slicing is a scenario axis, explain how that changes the entry point and branch structure.
Ask about multiple storage algorithms before assuming one shared temporal-storage path.
If the workflow uses CSVs or similar model-input tables, explicitly call out which temporal tables need rewriting.
If the workflow structure is underspecified, ask clarifying questions first instead of inventing stage names or ordering.

Create a surgical temporal slicing adjustment plan for the requested workflow. Use the `temporal-slicing-adjustment` skill and anchor the analysis in BCNexus when the target workflow is this repository. If the user's workflow stages are incomplete, unclear, or use unfamiliar naming, ask a small set of targeted clarification questions before producing the plan. In particular, ask about: - where temporal aggregation or representative-day logic currently happens - whether temporal slicing is part of the base workflow or a scenario axis of its own - whether the user wants timeslice adjustment to happen before scenario application, after scenario application, or differently for different scenario families - what stage applies non-temporal scenario changes - whether the scenario mechanism changes storage structure, temporal structure, demand/emissions/technology values, or some combination - whether the workflow has one storage algorithm or multiple storage algorithms - which storage algorithms are present and whether temporal slicing must work across all of them or only selected ones - what representation the model inputs use before export, such as CSVs, tables, dataframes, or `.dat` fragments - what stage exports the final model input package - what script, tool, or step performs preprocessing after export - whether the workflow is object-oriented, script-based, notebook-driven, or pipeline-based Use those answers to connect the target workflow back to the BCNexus stage pattern: - temporal shaping - non-temporal scenario overlay - final datafile export - preprocessing handoff Do not assume the user's scenario mechanism matches BCNexus. If temporal slicing itself is a scenario dimension, plan the entry point around that fact instead of forcing a pre-scenario temporal stage. If the user already gave enough workflow structure, do not ask extra questions. Required output: ## Clarifications Used - List the workflow-stage details the user provided or confirmed. - State whether temporal slicing is a base-workflow step or a scenario axis. - State whether the workflow has multiple storage algorithms and which ones matter for the plan. - If no clarification was needed, state that the existing context was sufficient. ## Workflow Position - State exactly where temporal slicing belongs in the workflow. - State what must happen before it and after it. - State whether that position changes when temporal slicing is treated as a scenario-specific branch. ## Control Path - Identify the controlling functions, scripts, stages, or modules. - For BCNexus, trace the path through `RunModel`, the builder temporal logic, scenario overlay, datafile export, and preprocessing. - For non-BCNexus workflows, explicitly map the user's stage names onto the equivalent BCNexus stages. ## Required Changes - List the minimum implementation steps needed. - Separate temporal metadata computation, temporal table rewrites, clustered profile rewrites, scenario overlay, and export/preprocessing handoff. ## Storage Scope - State whether the plan covers a single storage algorithm or multiple storage algorithms. - If the workflow uses storage structures beyond Niet or Kotzur, state that the BCNexus-derived guidance is only directly validated for Niet/Kotzur-style storage structures and explain any resulting uncertainty. ## Non-OOP Adaptation - If the target workflow is not object-oriented, rewrite the plan as a linear pipeline of functions or scripts. ## Validation - Give the narrowest checks that prove the temporal slicing wiring is correct. Constraints: - Keep the plan specific to the described workflow, not generic boilerplate. - Preserve the ordering required by the user's actual workflow. If temporal slicing is not a scenario axis, default to temporal shaping before non-temporal scenario overlay, and both before final datafile generation and preprocessing. - If temporal slicing is a scenario axis, explain how that changes the entry point and branch structure. - Ask about multiple storage algorithms before assuming one shared temporal-storage path. - If the workflow uses CSVs or similar model-input tables, explicitly call out which temporal tables need rewriting. - If the workflow structure is underspecified, ask clarifying questions first instead of inventing stage names or ordering.

{ "prompt": "Create a surgical temporal slicing adjustment plan for the requested workflow.\n\nUse the `temporal-slicing-adjustment` skill and anchor the analysis in BCNexus when the target workflow is this repository.\n\nIf the user's workflow stages are incomplete, unclear, or use unfamiliar naming, ask a small set of targeted clarification questions before producing the plan. In particular, ask about:\n- where temporal aggregation or representative-day logic currently happens\n- whether temporal slicing is part of the base workflow or a scenario axis of its own\n- whether the user wants timeslice adjustment to happen before scenario application, after scenario application, or differently for different scenario families\n- what stage applies non-temporal scenario changes\n- whether the scenario mechanism changes storage structure, temporal structure, demand/emissions/technology values, or some combination\n- whether the workflow has one storage algorithm or multiple storage algorithms\n- which storage algorithms are present and whether temporal slicing must work across all of them or only selected ones\n- what representation the model inputs use before export, such as CSVs, tables, dataframes, or `.dat` fragments\n- what stage exports the final model input package\n- what script, tool, or step performs preprocessing after export\n- whether the workflow is object-oriented, script-based, notebook-driven, or pipeline-based\n\nUse those answers to connect the target workflow back to the BCNexus stage pattern:\n- temporal shaping\n- non-temporal scenario overlay\n- final datafile export\n- preprocessing handoff\n\nDo not assume the user's scenario mechanism matches BCNexus. If temporal slicing itself is a scenario dimension, plan the entry point around that fact instead of forcing a pre-scenario temporal stage.\n\nIf the user already gave enough workflow structure, do not ask extra questions.\n\nRequired output:\n\n## Clarifications Used\n- List the workflow-stage details the user provided or confirmed.\n- State whether temporal slicing is a base-workflow step or a scenario axis.\n- State whether the workflow has multiple storage algorithms and which ones matter for the plan.\n- If no clarification was needed, state that the existing context was sufficient.\n\n## Workflow Position\n- State exactly where temporal slicing belongs in the workflow.\n- State what must happen before it and after it.\n- State whether that position changes when temporal slicing is treated as a scenario-specific branch.\n\n## Control Path\n- Identify the controlling functions, scripts, stages, or modules.\n- For BCNexus, trace the path through `RunModel`, the builder temporal logic, scenario overlay, datafile export, and preprocessing.\n- For non-BCNexus workflows, explicitly map the user's stage names onto the equivalent BCNexus stages.\n\n## Required Changes\n- List the minimum implementation steps needed.\n- Separate temporal metadata computation, temporal table rewrites, clustered profile rewrites, scenario overlay, and export/preprocessing handoff.\n\n## Storage Scope\n- State whether the plan covers a single storage algorithm or multiple storage algorithms.\n- If the workflow uses storage structures beyond Niet or Kotzur, state that the BCNexus-derived guidance is only directly validated for Niet/Kotzur-style storage structures and explain any resulting uncertainty.\n\n## Non-OOP Adaptation\n- If the target workflow is not object-oriented, rewrite the plan as a linear pipeline of functions or scripts.\n\n## Validation\n- Give the narrowest checks that prove the temporal slicing wiring is correct.\n\nConstraints:\n- Keep the plan specific to the described workflow, not generic boilerplate.\n- Preserve the ordering required by the user's actual workflow. If temporal slicing is not a scenario axis, default to temporal shaping before non-temporal scenario overlay, and both before final datafile generation and preprocessing.\n- If temporal slicing is a scenario axis, explain how that changes the entry point and branch structure.\n- Ask about multiple storage algorithms before assuming one shared temporal-storage path.\n- If the workflow uses CSVs or similar model-input tables, explicitly call out which temporal tables need rewriting.\n- If the workflow structure is underspecified, ask clarifying questions first instead of inventing stage names or ordering.", "variables": [], "notes": "Create a temporal slicing adjustment plan for BCNexus or another OSeMOSYS/CLEWs workflow. Use when you need a surgical implementation plan for hour grouping, representative-day clustering, temporal table rewrites, workflow phase ordering, or preprocessing handoff. Arguments: Describe the workflow, entry point, and timeslice change you want planned..", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/DeltaE/BC_Nexus", "path": ".github/prompts/timeslice-plan.prompt.md", "ref": "2bbceb68fca22cb9e06f6cc254cfe6aa40c1fc2c", "url": "https://github.com/DeltaE/BC_Nexus/blob/2bbceb68fca22cb9e06f6cc254cfe6aa40c1fc2c/.github/prompts/timeslice-plan.prompt.md", "key": "DeltaE/BC_Nexus/.github/prompts/timeslice-plan.prompt.md" } }, "model_hints": [ "GPT-5 (copilot)" ] }

timeslice-plan

About

Clarifications Used

Workflow Position

Control Path

Required Changes

Storage Scope

Non-OOP Adaptation

Validation

Use it

Manifest

Reviews