Laravel Development Workflow

An agent skill for shipping Laravel features and root-cause bug fixes with proportionate analysis, regression coverage, and verification.

It helps a coding agent answer the questions that matter before declaring a Laravel change complete:

• What observable behavior is supposed to change?
• Which scenarios, permissions, and edge cases are relevant?
• Does the implementation follow this application's existing architecture?
• What evidence proves the change works without a nearby regression?

Install

Install from the Skills directory:

npx skills add junaid-pk/laravel-development-workflow

The repository contains a standard SKILL.md, so it can also be used by tools that support the Agent Skills format.

Use

Once installed, ask your coding agent to build or fix something in an existing Laravel application. For example:

Fix the duplicate invoice bug in this Laravel app and add regression coverage.

Add manager approval to expense claims, preserving the current policy and notification patterns.

The skill guides the agent through a task-sized workflow:

1. Inspect the relevant Laravel behavior and repository conventions.
2. Define scenarios, edge cases, and acceptance criteria.
3. Reproduce bugs and trace their actionable root cause.
4. Implement within the application's existing architecture.
5. Run targeted tests, then the broader checks justified by the change.
6. Report concrete completion evidence and any unverified risk.

Design Choices

This workflow is deliberately proportionate. It does not require a new service, form request, factory, seeder, or Artisan command for every task. Those tools are used when the application already relies on them or when they materially improve the change.

It also does not assume a specific Laravel test stack. The agent discovers and uses the repository's own Pest or PHPUnit setup, static analysis, formatter, and CI conventions.

What It Covers

• Laravel feature development
• Root-cause bug diagnosis and repair
• Validation and authorization behavior
• Eloquent and database changes
• Events, notifications, queues, and API contracts
• Risk-based testing and verification

Safety

The workflow keeps changes inside the user's requested scope and preserves unrelated work already present in the repository. It does not authorize production commands, destructive database operations, credential changes, deployments, or external account actions; those require explicit project instructions or user direction.

Contributing

Issues and focused pull requests are welcome. Changes to the workflow should solve a demonstrated Laravel development failure mode without adding ceremony to unrelated tasks.

License

MIT