skills.rest
bramato
bramatoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-driven-development

Guides Laravel and React feature development through four structured phases from requirements to implementation.

Updated Feb 8, 2026
Search Tags:#workflow#design#react#requirements#implementation#laravel#spec-driven development
One-click install
npx skills add https://github.com/bramato/laravel-react-plugins --skill spec-driven-development-bramato
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/bramato/laravel-react-plugins/tree/main/laravel-react/skills/spec-driven-development
Command: npx skills add https://github.com/bramato/laravel-react-plugins --skill spec-driven-development-bramato

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a robust framework to manage the entire lifecycle of feature development, ensuring clarity, traceability, and adherence to design from initial requirements through to implementation.

Core Features & Use Cases

  • Structured Workflow: Guides users through four distinct phases: Requirements (EARS syntax), Technical Design, Task Planning, and Implementation.
  • Traceability: Links every implementation task back to specific requirements.
  • Approval Gates: Enforces mandatory user approval at critical stages (requirements and design).
  • Use Case: When starting a new complex feature like a user profile management system, use this Skill to first define requirements, then design the API and database schema, break down the implementation into manageable tasks, and finally execute those tasks systematically.

Quick Start

Use the spec-driven-development skill to start defining requirements for a new user authentication feature.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
What is spec-driven development for Laravel and React feature workflows?▼

Spec-driven development is a structured four-phase workflow guiding Laravel and React developers from requirements gathering to systematic implementation, ensuring traceability and design authority across the entire feature lifecycle.

How do I structure feature requirements using EARS syntax?▼

You can structure feature requirements using EARS syntax during the initial requirements phase, which enforces mandatory user approval gates before proceeding to technical design documentation and hierarchical task planning.

How do I plan and execute full-stack feature implementation tasks systematically?▼

You can execute full-stack implementation systematically by following a hierarchical task planning phase that links every implementation task back to specific requirements and technical design documents.

Does this spec-driven workflow require approval before coding begins?▼

Yes, the workflow enforces mandatory user approval at critical stages, specifically after requirements gathering and technical design documentation, ensuring collaboration and adherence to design before implementation execution.

When should I use a structured spec workflow for feature development?▼

You should use a structured spec workflow when developing complex full-stack features, such as a user profile management system, where clarity, traceability, and adherence to design from requirements through code are critical.

Related Skills

Explore More Software Engineering Skills→
AirMileAirMile

dev-define

Define feature requirements and architecture from project backlog and plans.

Community
Advanced
nikhil02032022nikhil02032022

crm-module-builder

Generate Laravel and Blade CRM modules from BRD requirements.

Community
Advanced
SoltusSoltus
1

spec-workflow

Guide software engineering workflows through requirement analysis, technical design, and task planning.

Community
Advanced
barkleesandersbarkleesanders
5

ralph

Generate dependency-ordered user stories and enforce quality gates during autonomous feature builds.

Community
Intermediate