Prompt Builder Compatibility Skill
Goal
Preserve legacy prompt-builder activation while routing all source changes, review, behavior testing, validation, and outcome resolution through the hve-builder skill.
Flow
- Translate
promptFiles to targets. Treat files as reference context unless the caller explicitly includes them in the write boundary.
- Resolve
create when an approved target is missing and improve when targets already exist. Route explicit cleanup to the prompt-refactor compatibility skill and read-only analysis to prompt-analyze.
- Activate
hve-builder with the targets, selected mode, requirements, reference context, and any caller-owned evidence root.
- Return the
hve-builder final response without adding a second author, test, or evaluation loop.
Inputs
promptFiles: target prompt-engineering artifacts; defaults to current open or attached filesfiles: reference artifacts used to derive requirementsrequirements: explicit objectives, constraints, and acceptance criteriaevidenceRoot: optional caller-owned HVE Builder evidence path
Success Criteria
- Legacy inputs map to an explicit HVE Builder target set and write boundary.
hve-builder completes every required gate for the selected mode.- The returned overall outcome is unchanged from
hve-builder.
Constraints
- Do not dispatch retired named lifecycle workers.
- Do not maintain a second sandbox, status vocabulary, or quality rubric.
- Do not treat reference files as write targets without explicit approval.
Stop Rules
- Stop when
hve-builder returns Pass, Revise, Deferred, or Blocked.
- Ask only when target identity or write authority cannot be inferred safely.
Handoff
Use prompt-analyze for a legacy read-only request and prompt-refactor for a legacy behavior-preserving cleanup request. Both route back to hve-builder.
Final Response Contract
Return the mode, targets, changed files, static verdict, behavior-test fidelity and verdict, validation result, overall outcome, evidence links, and next action.
1---2name: prompt-builder3description: Compatibility alias for legacy prompt-building requests. Routes creation and improvement to the hve-builder skill.4license: MIT5---6
7# Prompt Builder Compatibility Skill
8
9## Goal
10
11Preserve legacy `prompt-builder` activation while routing all source changes, review, behavior testing, validation, and outcome resolution through the `hve-builder` skill.
12
13## Flow
14
151. Translate `promptFiles` to `targets`. Treat `files` as reference context unless the caller explicitly includes them in the write boundary.
162. Resolve `create` when an approved target is missing and `improve` when targets already exist. Route explicit cleanup to the `prompt-refactor` compatibility skill and read-only analysis to `prompt-analyze`.
173. Activate `hve-builder` with the targets, selected mode, requirements, reference context, and any caller-owned evidence root.
184. Return the `hve-builder` final response without adding a second author, test, or evaluation loop.
19
20## Inputs
21
22* `promptFiles`: target prompt-engineering artifacts; defaults to current open or attached files
23* `files`: reference artifacts used to derive requirements
24* `requirements`: explicit objectives, constraints, and acceptance criteria
25* `evidenceRoot`: optional caller-owned HVE Builder evidence path
26
27## Success Criteria
28
29* Legacy inputs map to an explicit HVE Builder target set and write boundary.
30* `hve-builder` completes every required gate for the selected mode.
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 maintain a second sandbox, status vocabulary, or quality rubric.
37* Do not treat reference files as write targets without explicit approval.
38
39## Stop Rules
40
41* Stop when `hve-builder` returns Pass, Revise, Deferred, or Blocked.
42* Ask only when target identity or write authority cannot be inferred safely.
43
44## Handoff
45
46Use `prompt-analyze` for a legacy read-only request and `prompt-refactor` for a legacy behavior-preserving cleanup request. Both route back to `hve-builder`.
47
48## Final Response Contract
49
50Return the mode, targets, changed files, static verdict, behavior-test fidelity and verdict, validation result, overall outcome, evidence links, and next action.
gabrielmoreira