specmint-tdd-htmllisted

TDD-first spec management for AI coding workflows, producing canonical SPEC.html files with red-green-refactor state. Use this companion when the user explicitly mentions specs, forging, structured planning, resume/status, implementing a spec, red-green-refactor, or running tests. Do NOT trigger on ordinary coding tasks that do not ask for spec management.
ngvoicu/kluris · ★ 4 · Testing & QA · score 77

Install: claude install-skill ngvoicu/kluris

# Spec Mint TDD HTML — Kluris Companion Turn feature requests into HTML specs and implement them with strict TDD. This HTML variant uses `.specs/<id>/SPEC.html` as the canonical spec document. The HTML file carries metadata, acceptance criteria, phases, TEST/IMPL task pairs, `data-status` progress, `data-tdd-phase` red-green-refactor state, diagrams, code previews, the TDD log, decisions, and deviations. When this file is referenced from a Kluris-generated brain skill, read and follow it directly from `~/.kluris/companions/specmint-tdd-html/SKILL.md`. Do not ask the user to install Specmint separately. Kluris vendors companions as single `SKILL.md` files, so every rule needed for companion mode is below. ## Critical Invariants 1. **Canonical files** - Registry: `.specs/registry.md` (markdown index) - Per-spec document: `.specs/<id>/SPEC.html` - Research notes: `.specs/<id>/research-*.md` - Interview notes: `.specs/<id>/interview-*.md` - Scratch, if needed: `.specs/<id>/artifacts/` 2. **Authority rule**: the JSON inside `<script type="application/json" id="spec-meta">` is authoritative for identity and spec status. `data-status` attributes on phases, tasks, and acceptance criteria are authoritative for progress. `data-tdd-phase` on implementation tasks records `red`, `green`, or `refactor` state when a cycle is in progress. 3. **TDD invariant**: no production code without a failing test. Capture the RED failure before writing implementation, m