Laravel Development Workflow

Make the requested Laravel behavior correct, maintainable within the existing application, and supported by evidence that matches the change's risk.

When to Use

• Use when implementing a feature in an existing Laravel application.
• Use when diagnosing and fixing a Laravel bug at its actionable root cause.
• Use when a Laravel change needs regression coverage and proportionate verification.
• Use when the project already has architectural or testing conventions that must be preserved.

Establish the Contract

Before editing:

• Read the repository instructions and inspect the relevant routes, models, controllers, actions or services, requests, policies, jobs, events, tests, and schema.
• Trace the current behavior far enough to identify the actual change boundary and existing conventions.
• Turn the request into a compact set of scenarios, important edge cases, and verifiable acceptance criteria. Keep this analysis in the working notes unless the user requests a separate artifact.
• Identify authorization, validation, transaction, queue, cache, and concurrency concerns only where they can affect this behavior.