HVE Builder Skill

Goal

Deliver a usable prompt, instruction, agent, subagent, or skill that meets the requirements catalog, or a credible read-only report, with the fewest lifecycle turns that preserve an independent review pass and final-state evidence.

Read references/workflow-contract.md first; it owns mode routing, candidate convergence, the review pass, and overall outcomes. Apply references/requirements-catalog.md as the quality standard. The References section maps the remaining on-demand references.

Use Cases

• Create a new artifact from a stated need, choosing the type by responsibility and activation through references/artifact-types.md.
• Turn an existing draft, prompt, or ad hoc instruction set into an artifact that meets the catalog, preserving its contract unless the caller asks for a change.
• Clean up an existing artifact by keeping required guidance, clarifying incomplete rules, consolidating duplication, and retiring obsolete instructions. Use the catalog's maintenance decisions to distinguish behavior-preserving refactoring from an approved replacement or removal.
• Review instruction quality without changing source, or validate mechanical conformance without claiming an instruction-quality verdict.
• Extend an HVE workflow with project-specific capability. For example, a team that wants rpi-research and rpi-plan to use an internal corpus needs a skill that tells those workflows how to gather, index, and cite that corpus, or a research subagent that gathers source pointers in isolated context and returns them as suggestions. Choose between them by whether the work needs its own context, and author against the target workflow's discovery contract in references/extending-hve-builder.md; for an RPI phase, the artifact description is the contract the phase follows.
• Author a host extension (instruction, skill, or subagent) that hve-builder itself discovers in a downstream repository.

Modes