prompt-builder
작성자: microsoft
전체 프롬프트 빌더 단계 루프를 통해 프롬프트 아티팩트를 생성하거나 업데이트하고, 리팩터 및 분석 요청을 전문 스킬로 라우팅합니다.
npx skills add https://github.com/microsoft/hve-core --skill prompt-builderPrompt 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
promptFilestotargets. Treatfilesas reference context unless the caller explicitly includes them in the write boundary. - Resolve
createwhen an approved target is missing andimprovewhen targets already exist. Route explicit cleanup to theprompt-refactorcompatibility skill and read-only analysis toprompt-analyze. - Activate
hve-builderwith the targets, selected mode, requirements, reference context, and any caller-owned evidence root. - Return the
hve-builderfinal 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-buildercompletes every required gate for the selected mode.- The returned overall outcome is unchanged from
hve-builder.
Constraints
- Do not dispatch
Prompt Tester,Prompt Evaluator, orPrompt Updater. - 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-builderreturns 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.