implement-spec

Implement spec phases with inline progress tracking and verification before PR creation.

214|2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/SanderMuller/laravel-fluent-validation --skill implement-spec-sandermuller
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-spec
Source: https://github.com/SanderMuller/laravel-fluent-validation/tree/main/.ai/skills/implement-spec
Command: npx skills add https://github.com/SanderMuller/laravel-fluent-validation --skill implement-spec-sandermuller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements a phase-by-phase spec execution workflow with inline progress tracking directly in the spec file.

Core Features & Use Cases

  • Read and understand the spec, identify phases, implement phases, log findings, verify, and create PR.
  • Supports continuing work across phases with Open Questions management and Findings logging.
  • Encourages incremental verification and a final verification gate before PR.

Quick Start

Begin by reading the spec, identifying the next unchecked phase, and implementing its tasks.

Frequently Asked Questions about implement-spec

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

FAQPage Schema
How do I automate phase-by-phase implementation from a specification file?

A phase-by-phase implementation workflow automates reading a full spec, identifying sequential phases, implementing tasks, and tracking progress directly inline within the spec file. It enforces disciplined coding by requiring test coverage and explicit logging for each phase.

How do I track implementation progress and open questions within a spec file?

Tracking progress within a spec file involves logging findings and managing open questions explicitly inline as you implement each phase. This supports iterative development by keeping decisions and phase completion status visible directly in the specification document.

What is the best way to manage incremental verification before creating a pull request?

Managing incremental verification before a pull request involves enforcing a final verification gate after completing all spec phases. This workflow requires test coverage and explicit logging of decisions throughout implementation to support a thorough final review.

Can I continue implementation across multiple phases if I stop mid-work?

Yes, you can continue implementation across phases by identifying the next unchecked phase in the specification. The workflow supports resuming work by reading the spec, finding incomplete phases, and reviewing open questions and findings logged from previous sessions.

Does this spec execution workflow require test coverage for each phase?

Yes, this spec execution workflow requires test coverage for each phase. It enforces disciplined coding practices, ensuring every identified phase in the specification is accompanied by tests and explicit logging of decisions before proceeding.