specgen-laravel-eloquent-bladehtmx

To generate Laravel specification docs, the skill aggregates CLAUDE.md, PRD.md, and mockup data to produce a root SPECIFICATION.md and per-module SPEC.md files. This maps user stories, NFRs, and constraints to implementation artifacts with version-aware traceability.

Document a Laravel monolith with Blade and HTMX by deriving architectural decisions from project context. This produces a structured blueprint that ensures consistent traceability across modules, data models, services, and UI surfaces for modular packaging.

Map user stories and NFRs to Laravel modules by validating optional component selections and version gating against architecture principles and CHANGELOGs. This produces per-module SPEC.md files aligning business requirements with technical design.

Yes, you can validate version gating against CHANGELOGs and architecture principles before producing outputs. The skill governs scope and acceptance criteria across modules by checking optional component selections and version constraints.

To prepare a module-specific specification blueprint, you need CLAUDE.md, PRD.md, and MOCKUP data. The skill infers application module requirements by aggregating these inputs to document modules, data models, services, and UI surfaces.