docs/agent

Name: docs/agent
Availability: InStock
Author: leroystolberg-hash

Convert TVL specification requirements into TypeScript code with phase-gated compilation and test gates.

Updated Mar 10, 2026

Search Tags:#typescript #vitest #spec-driven development #tool virtualization layer #phase-based roadmap #pino logging

Ready to run

npx skills add https://github.com/leroystolberg-hash/TVL --skill docs-agent-leroystolberg-hash

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs/agent
Source: https://github.com/leroystolberg-hash/TVL/tree/main/docs
Command: npx skills add https://github.com/leroystolberg-hash/TVL --skill docs-agent-leroystolberg-hash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It translates the TVL specifications into production-ready TypeScript implementations by providing a strict, phase-based execution workflow for an OpenClaw TVL Codex agent.

Core Features & Use Cases

Spec-driven implementation: Treats TVL_SPEC.md as the only source of truth and prevents feature creep by requiring TODOs when information is missing.
Phase-gated delivery: Enforces the roadmap order from Phase 1 through Phase 12, with compilation and test requirements for each phase before moving on.
Production-grade engineering rules: Requires TypeScript strictness, ESM style, structured pino logging, typed custom errors, deterministic execution patterns, and correct SQLite usage.

Quick Start

Ask the Codex agent to implement Phase 1 by reading TVL_SPEC.md, following the required folder structure, compiling with tsc --noEmit, and running vitest until all Phase 1 tests pass.

Frequently Asked Questions about docs/agent

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

FAQPage Schema

How do I generate production-ready TypeScript code from a specification?▼

You generate production-ready TypeScript from a spec by treating the spec file as the single source of truth and enforcing strict ESM rules, typed errors, and test gates during implementation. This prevents feature creep by requiring TODOs for missing spec details.

What is phase-gated spec-driven development in TypeScript?▼

Phase-gated spec-driven development enforces a strict roadmap order, requiring successful TypeScript compilation and vitest test passage for each phase before advancing to the next. This ensures production-grade modules are built sequentially with deterministic execution patterns.

How do I implement strict TypeScript ESM modules with vitest testing?▼

To implement strict TypeScript ESM modules with vitest, you enforce strict typing, use structured pino logging, apply typed custom error handling, and run vitest until all phase-specific tests pass. Compilation with tsc --noEmit is also required before advancing.

Does spec-driven TypeScript development work with SQLite and pino logging?▼

Yes, spec-driven TypeScript development integrates with SQLite by enforcing correct database constraints, and uses pino for structured logging. These requirements ensure deterministic execution and production-grade error handling across the implemented modules.

What are the limitations of phase-based TypeScript code generation?▼

The limitation of phase-based code generation is that you cannot skip phases; each phase requires passing both TypeScript compilation and vitest tests before proceeding. Additionally, you are restricted to only using dependencies explicitly allowed by the specification.

Why does my TypeScript spec implementation require TODOs for missing information?▼

Your TypeScript spec implementation requires TODOs for missing information to strictly prevent feature creep and ensure the specification remains the only source of truth. This enforces spec-driven development by halting assumptions until the spec is updated.