artifacts

Capture project context and decisions into structured milestone artifacts.

77|5|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/lee-to/hlv --skill artifacts-lee-to
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: artifacts
Source: https://github.com/lee-to/hlv/tree/main/skills/artifacts
Command: npx skills add https://github.com/lee-to/hlv --skill artifacts-lee-to

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The artifact interview tool helps teams capture domain context, architectural decisions, constraints, and unknowns in a structured way to preserve project knowledge across milestones.

Core Features & Use Cases

  • Guided Blocks: Collect domain context, features, infrastructure decisions, constraints, and unknowns in a consistent format.
  • Milestone-scoped artifacts: Create and organize files under human/milestones/{id}/artifacts/ for milestone-specific outputs.
  • Incremental mode: Read existing artifacts and update only the parts that have changed.
  • Open questions tracking: Capture missing information and risks for later resolution.

Quick Start

Follow the on-screen prompts to fill in domain context, features, constraints, decisions, and unknowns for the active milestone.

Frequently Asked Questions about artifacts

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

FAQPage Schema
How do I capture project context and architectural decisions consistently across milestones?

You can capture project context and architectural decisions using structured interview prompts that collect domain context, features, constraints, and unknowns. This ensures comprehensive project knowledge is preserved in designated artifact directories for later review.

What is the best way to document project unknowns and open questions for later resolution?

Documenting project unknowns involves tracking missing information and risks during structured interviews. The captured open questions are stored within milestone-specific artifact files, creating a clear audit trail for later resolution by the team.

Can I update existing architectural documentation incrementally without rewriting everything?

Yes, you can update existing architectural documentation incrementally. The tool reads current artifacts and modifies only the specific parts that have changed, preserving previous context while appending new decisions and domain information to the audit trail.

How do I organize milestone-specific documentation and architectural artifacts?

You organize milestone-specific documentation by creating and managing files under the human/milestones/{id}/artifacts/ directory structure. This separates global project context from milestone-scoped outputs, keeping artifact files cleanly organized by their specific milestone identifier.

What information do I need to provide to generate comprehensive project artifacts?

To generate project artifacts, you must provide domain context, software features, infrastructure constraints, architectural decisions, and current unknowns. The guided interview prompts structure this input into a consistent format for your designated artifact directories.