sdd-html

Orchestrate HTML spec-driven development workflows with phase-gated routing.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/HexSleeves/skills --skill sdd-html
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-html
Source: https://github.com/HexSleeves/skills/tree/main/skills/sdd-html
Command: npx skills add https://github.com/HexSleeves/skills --skill sdd-html

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill keeps spec-driven development organized by turning an idea into a phased HTML workflow with clear approvals, artifacts, and validation gates, so agents can plan and execute changes without losing traceability.

Core Features & Use Cases

  • Spec generation: Creates HTML specifications, or clarification questions when context is insufficient.
  • Task planning and audits: Breaks specs into parent tasks, sub-tasks, relevant files, and planning audits before implementation.
  • Implementation tracking and validation: Manages task status, proof artifacts, and validation reports with strict pass/fail gates.
  • Lavish-friendly review: Optionally opens HTML artifacts in Lavish Editor for interactive browser review.
  • Use case: A developer asks for a new feature, then uses this Skill to move from spec to tasks, implementation, proof, and validation in one coherent repository workflow.

Quick Start

Ask the sdd-html skill to create the next HTML phase artifact for your repository, starting with a new spec or continuing an existing spec through tasks, implementation, or validation.

Frequently Asked Questions about sdd-html

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

FAQPage Schema
How do I manage spec-driven development workflows for AI agents in HTML?▼

Spec-driven development workflows in HTML are managed by orchestrating phased spec creation, task planning, implementation tracking, proof artifacts, and validation gates across a single active spec to maintain traceability.

What is the best way to create phased validation artifacts for repository tasks?▼

Creating phased validation artifacts involves breaking specifications into parent tasks, sub-tasks, and relevant files, then managing task status and proof artifacts through strict pass/fail validation gates.

How does phase-gated routing work for HTML specifications?▼

Phase-gated routing enforces strict workflow-state detection with immutable file naming conventions, ensuring AI agents move sequentially from spec creation to task planning, implementation, and final validation.

Can I open HTML workflow artifacts in Lavish Editor for interactive review?▼

Yes, HTML workflow artifacts can optionally be opened in Lavish Editor for interactive browser review, provided an availability check is passed during the workflow-state detection phase.

What happens when there is insufficient context to generate an HTML specification?▼

When context is insufficient to generate an HTML specification, the workflow automatically prompts clarification questions to gather the necessary repository details before proceeding with task planning.

Do I need specific file naming conventions for spec-driven HTML workflows?▼

Yes, spec-driven HTML workflows require strict immutable file naming conventions to ensure reliable workflow-state detection and accurate phase-gated routing throughout the implementation tracking process.