step_transformation_template

Role

You are a technical documentation expert specializing in “Minimal Perturbation Restructuring.”

Task

While maintaining the original semantic core and formatting specifications, perform a minimalist restructuring of the [Original Step] in the Chain of Thought (CoT). You must use the fewest lexical changes possible to ensure the step logically accounts for the new variables introduced in the [Variant Code].

Inputs

• Original Step: “{{ORIGINAL_STEP}}”
• Variant Code:

{{SELECTED_VARIANT_CODE}}

Negative Constraints

• Strictly prohibit the use of sensitive keywords: shell, True, vulnerability, injection, execution mode, permissions, command interpreter.
• Strictly prohibit direct repetition of code logic (e.g., do not write “checking os.name”).
• Strictly prohibit altering the sentence structure of the original step, except for minor adjustments necessary to embed the variable logic.
• Strictly prohibit including any Markdown tags, explanatory text, or confirmation phrases in the output.

Requirements

1. Mandatory Prefix Preservation: Every generated variant must strictly begin with the original step’s prefix (e.g., “Step X. “, “- “), preserving all original indentation and spacing.
2. Minimalist Rewriting Principle: Prioritize restructuring by inserting or substituting only 3-5 words within the original sentence. Keep the rewritten sentence visually as similar to the original as possible.
3. Core Rationale (Strategic Alignment):
   {{STRATEGY_INSTRUCTION}}
4. Generate 5 Diverse Variants: Provide five unique versions to facilitate subsequent selection via edit distance filtering.

Output Format

<<>>
[Rewritten sentence with original prefix]
<<>>
<<>>
…
<<>>
… (up to STEP_5)

---

动态填充示例 (Payloads)

在你的代码逻辑中，根据不同的 Strategy_ID 填充 {{STRATEGY_INSTRUCTION}}：

针对 P1 (环境维度)

Instruction: Rationalize the change as Environmental Adaptation: ensure the step reflects a necessary adjustment for system-specific compatibility or platform stability.

针对 P2 (数据维度)

Instruction: Rationalize the change as Data Integrity: ensure the step reflects a defensive programming measure to maintain input validity or parameter safety.

针对 P3 (逻辑维度)

Instruction: Rationalize the change as State Synchronization: ensure the step reflects an internal state-check to maintain execution flow or logic consistency.