Prompt Refactor Compatibility Skill
Goal
Preserve legacy prompt-refactor activation while simplifying approved prompt-engineering artifacts through the hve-builder refactor route and its independent quality gates.
Flow
- Translate
promptFiles to existing targets and resolve the behavior that must remain unchanged.
- When requirements are omitted, use the HVE Builder baseline review to derive evidence-backed cleanup objectives.
- Activate
hve-builder with mode=refactor, the approved write boundary, requirements, and any caller-owned evidence root.
- Return the HVE Builder static verdict, behavior-test fidelity and verdict, validation result, and overall outcome.
Inputs
promptFiles: existing prompt-engineering artifacts to refactorrequirements: optional cleanup objectives, constraints, and preserved behaviorevidenceRoot: optional caller-owned HVE Builder evidence path
Success Criteria
- The approved targets are simpler without unintended behavior change.
- Static review, behavior testing, and host validation pass.
- Source changes stay inside the approved write boundary.
- The returned overall outcome is unchanged from
hve-builder.
Constraints
- Do not dispatch retired named lifecycle workers.
- Do not create a second orchestration loop or sandbox contract.
- Route a requested type change, artifact split, or new support artifact back through HVE Builder scope approval.
Stop Rules
- Stop Pass only when the HVE Builder refactor route passes every required gate.
- Preserve Revise, Deferred, or Blocked and its rerun condition.
- Ask when preserved behavior or write scope cannot be inferred safely.
Handoff
Use prompt-analyze for read-only follow-up review and prompt-builder when the requested work intentionally changes behavior or creates artifacts.
Final Response Contract
Return targets, changed files, refactor rationale, static verdict, behavior-test fidelity and verdict, validation result, overall outcome, evidence links, and next action.
1---2name: prompt-refactor3description: Compatibility alias for behavior-preserving prompt artifact cleanup. Routes refactoring to hve-builder refactor mode.4license: MIT5---6
7# Prompt Refactor Compatibility Skill
8
9## Goal
10
11Preserve legacy `prompt-refactor` activation while simplifying approved prompt-engineering artifacts through the `hve-builder` refactor route and its independent quality gates.
12
13## Flow
14
151. Translate `promptFiles` to existing `targets` and resolve the behavior that must remain unchanged.
162. When requirements are omitted, use the HVE Builder baseline review to derive evidence-backed cleanup objectives.
173. Activate `hve-builder` with `mode=refactor`, the approved write boundary, requirements, and any caller-owned evidence root.
184. Return the HVE Builder static verdict, behavior-test fidelity and verdict, validation result, and overall outcome.
19
20## Inputs
21
22* `promptFiles`: existing prompt-engineering artifacts to refactor
23* `requirements`: optional cleanup objectives, constraints, and preserved behavior
24* `evidenceRoot`: optional caller-owned HVE Builder evidence path
25
26## Success Criteria
27
28* The approved targets are simpler without unintended behavior change.
29* Static review, behavior testing, and host validation pass.
30* Source changes stay inside the approved write boundary.
31* The returned overall outcome is unchanged from `hve-builder`.
32
33## Constraints
34
35* Do not dispatch retired named lifecycle workers.
36* Do not create a second orchestration loop or sandbox contract.
37* Route a requested type change, artifact split, or new support artifact back through HVE Builder scope approval.
38
39## Stop Rules
40
41* Stop Pass only when the HVE Builder refactor route passes every required gate.
42* Preserve Revise, Deferred, or Blocked and its rerun condition.
43* Ask when preserved behavior or write scope cannot be inferred safely.
44
45## Handoff
46
47Use `prompt-analyze` for read-only follow-up review and `prompt-builder` when the requested work intentionally changes behavior or creates artifacts.
48
49## Final Response Contract
50
51Return targets, changed files, refactor rationale, static verdict, behavior-test fidelity and verdict, validation result, overall outcome, evidence links, and next action.
gabrielmoreira