docs/agent

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.

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.

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.

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.

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.

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.