laravel:writing-plans

Convert confirmed Laravel designs into structured implementation plans with testable tasks.

Updated Mar 30, 2026

Search Tags:#planning #tdd #migrations #laravel #services #quality-gates #task-breakdown

Ready to run

npx skills add https://github.com/Patkik/Multi-tenant-SaaS-Catering-V2 --skill laravel-writing-plans-patkik

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: laravel:writing-plans
Source: https://github.com/Patkik/Multi-tenant-SaaS-Catering-V2/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/Patkik/Multi-tenant-SaaS-Catering-V2 --skill laravel-writing-plans-patkik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a reliable, repeatable process to transform a confirmed design into an actionable Laravel implementation plan consisting of bite-sized tasks, guardrails, and validation checkpoints.

Core Features & Use Cases

Scaffolding & Planning: Runner selection, workspace prep, and branch/worktree setup to ensure a clean starting point.
Data Model & Migrations: Define migrations and factories with one-commit-per-change, plus seeders for demo flows when needed.
Services & Interfaces: Controllers/Requests/Resources (or actions), ports & adapters for external systems, and jobs/events/listeners as necessary.
Tests (TDD): Feature tests covering behavior and unit tests for pure logic, using factories and a failure-first approach.
Quality Gates: Static analysis, linting, and test hygiene to keep the codebase passing.
Rollout & Observability: Logging and metrics integration, horizon queues, and flag-based rollout safety.

Quick Start

Provide a confirmed Laravel design and watch it transform into a structured, testable plan with tasks and acceptance criteria.

Frequently Asked Questions about laravel:writing-plans

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

FAQPage Schema

How do I turn a confirmed Laravel design into actionable development tasks?▼

To turn a confirmed Laravel design into actionable tasks, you need a structured planning process that breaks down scaffolding, data models, services, and TDD into small, testable steps with clear acceptance criteria. This approach transforms designs into bite-sized implementation sequences.

What is the best way to plan Laravel migrations and factories for a new feature?▼

The best way to plan Laravel migrations and factories is to define them with a one-commit-per-change approach. This ensures your data model planning includes discrete, testable tasks for schema changes, demo seeders, and validation checkpoints.

How do I structure a Laravel TDD plan for services and controllers?▼

Structuring a Laravel TDD plan involves sequencing tasks for controllers, requests, resources, and ports for external systems. It uses a failure-first approach to define feature tests covering behavior and unit tests for pure logic using factories.

Do I need a confirmed design before planning Laravel implementations?▼

Yes, you need a confirmed design before planning Laravel implementations. The planning process requires a finalized design as input to reliably transform it into a structured, testable plan with concrete tasks, guardrails, and rollout observability.

How to plan quality gates and rollout observability for Laravel projects?▼

To plan quality gates and rollout observability for Laravel projects, define tasks for static analysis, linting, and test hygiene. Include steps for logging, metrics integration, horizon queues, and flag-based rollout safety in your implementation sequence.