generate

Transform milestone artifacts into structured contracts, validation specs, and implementation plans.

77|5|Updated Mar 9, 2026

Search Tags:#planning #validation #artifacts #milestones #traceability #generate #contracts

Ready to run

npx skills add https://github.com/lee-to/hlv --skill generate-lee-to

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate
Source: https://github.com/lee-to/hlv/tree/main/skills/generate
Command: npx skills add https://github.com/lee-to/hlv --skill generate-lee-to

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HLV Generate transforms milestone artifacts into formal contracts, validation specs, and an actionable implementation plan, reducing ambiguity and iteration cycles.

Core Features & Use Cases

Converts milestone artifacts and global context into structured contracts, test-specs, and a staged plan.
Maintains traceability between artifacts, contracts, and tests, enabling easier audits and changes.
Generates open questions when artifacts are missing details, ensuring safe, incremental evolution of the project.

Quick Start

Place milestone and global artifacts under human/artifacts and milestone/artifacts, then invoke the generate skill to produce contracts, test-specs, and a milestone plan.

Frequently Asked Questions about generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn milestone artifacts into structured contracts and validation specs?▼

To turn milestone artifacts into structured contracts and validation specs, place your milestone and global artifacts in the human/artifacts and milestone/artifacts directories. The tool then transforms them into formal contracts, test-specs, and a staged implementation plan.

What is the best way to maintain traceability between project artifacts and contracts?▼

The best way to maintain traceability is to generate contracts and validation specs directly from your milestone artifacts. This approach enforces source-to-output traceability, linking artifacts, contracts, and tests to enable easier audits and changes.

How does artifact formalization handle missing details in project requirements?▼

Artifact formalization handles missing details by generating open questions when artifacts lack necessary information. This ensures safe, incremental evolution of the project by prompting you to clarify ambiguities before producing the final implementation plan.

Do I need specific dependencies to generate contracts and test-specs from artifacts?▼

You do not need specific dependencies to generate contracts and test-specs from artifacts. The skill operates independently, requiring only your milestone and global artifacts placed in the correct human and milestone artifact directories to function.

Can I use this approach for projects requiring incremental evolution and audits?▼

Yes, you can use this approach for projects requiring incremental evolution and audits. It converts milestone artifacts into structured contracts and test-specs, maintaining traceability and generating open questions to safely manage missing information.