domains / families / software-engineering / laravel-development-workflow

laravel-development-workflow

authentic

Build and fix existing Laravel applications through root-cause diagnosis, repository-native implementation, regression coverage, and risk-based verification.

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.

When not to use

• This workflow requires an existing Laravel application and adapts to that repository's architecture and tooling; it does not impose a complete project structure.
• It cannot prove production behavior when the required services, data, credentials, or environment are unavailable, so any unverified risk must be reported explicitly.
• It does not authorize destructive database work, production changes, deployments, credential changes, or external account actions.

Skill page

Source