Statamic Magic Actions Laravel Package

Product Decisions This Supports

• AI/LLM feature delivery in Laravel: This package sits in the LLM integration layer around Prism, so it supports decisions such as adding chat, summarization, structured extraction, classification, or lightweight agent-like workflows without building provider abstractions from scratch. Because the package is still 0.x, treat it as an accelerator for prototypes, internal tools, and MVPs rather than a foundation for revenue-critical paths until its versioning and compatibility policy stabilize.
• Build vs. buy/adopt: Adopt when the team is Laravel-first and already standardizing on Prism; the package reduces glue-code effort and keeps LLM calls closer to Laravel conventions. Reassess if the team needs multi-provider routing, strict upgrade guarantees, or enterprise governance — in those cases a direct Prism integration or a custom wrapper may be lower risk.
• Roadmap sequencing: Use this package to validate provider-agnostic LLM calls in a time-boxed spike before committing roadmap scope to AI features. v0.2.2 specifically unblocks installation alongside Prism 0.100, so teams can include a Prism minor upgrade in the roadmap without forking or abandoning the package.
• Use cases: Internal copilots, content drafting, extraction/classification pipelines, RAG prototypes, and Laravel apps that need a small integration surface over Prism rather than a full AI platform.

When to Consider This Package

• Consider it when: the team is Laravel/PHP-native, already uses Prism, wants a thin integration layer rather than a bespoke LLM client, and can tolerate 0.x versioning plus Composer caret constraints that pin Prism minors. It is a good fit for prototypes, MVPs, internal workflows, and teams that value Laravel conventions over raw SDK control.
• Look elsewhere when: you need long-term API stability, SLAs, enterprise governance, or multi-provider routing with strict compatibility guarantees. Also avoid it if the product depends on capabilities not exposed by Prism itself. The v0.2.2 release is maintenance-only — Prism 0.100 compatibility, CI coverage across both supported Prism minors, and a Dependabot configuration repair — not a new feature release. The Dependabot fix is a positive maintenance signal, but it also shows the project is still maturing its dependency automation.

How to Pitch It (Stakeholders)

Executives and engineering: This is an early-stage Laravel package that can reduce time-to-ship for LLM-backed features by leveraging Prism, but it is still 0.x and tightly coupled to Prism minor releases. v0.2.2 is a patch release with no breaking changes: it allows Prism 0.100 alongside 0.99, adds CI coverage for both supported Prism minors, and repairs Dependabot so Composer updates use the widen strategy. Net effect: lower integration friction and better maintenance hygiene, but no new product capability. Recommendation: use it for a time-boxed pilot or internal workflow, keep an abstraction boundary so it can be swapped, and avoid committing it to customer-critical roadmap items until versioning stabilizes. Engineering should pin and test Prism minors explicitly; product should treat AI capabilities as experimental until cost, latency, and provider behavior are validated.