Wizard Annotation Bundle Laravel Package

Product Decisions This Supports

• Wizard/flow architecture: Informs whether multi-step state (onboarding, checkout, KYC, application intake) lives in controller methods + session versus client-side step components.
• Build vs. buy for step orchestration: This is a thin, annotation-driven pattern — one controller method per step, validation gates before advancing. That pattern is cheap to reproduce in-house, which argues against taking a dependency for it.
• Roadmap scoping and effort estimates: If the team is on legacy Symfony with annotation routing, this could save a few days on a linear wizard. On Laravel or modern Symfony, it's a port/migration cost, not a saving.
• Stack hygiene decisions: Evidence for keeping wizard logic framework-native rather than adopting micro-packages that we'd have to own.

When to Consider This Package

Consider it only when:

• You have an existing Symfony app pinned to the annotations era (Symfony 3.x/4.x) where the bundle's assumptions still hold.
• The flow is linear, server-rendered, and simple — per-step validation, no branching, no draft persistence.
• You are willing to vendor/fork and own maintenance; the surface area is small, so the fork risk is bounded.

Look elsewhere when:

• You're on Laravel. This is a Symfony bundle, not a Laravel package — no service provider, no Laravel integration, despite being categorized as a Laravel/PHP package. Use Livewire/Inertia stepped components or a session-backed controller with Form Requests.
• You're on Symfony 5.4+/6/7. Annotations are deprecated in favor of PHP attributes, and 0 stars / 0 dependents / score 0 signals an unmaintained package with no PHP 8.x or Symfony 6+ guarantees and no security response path.
• The wizard branches, resumes, or needs persistence. Use Symfony Workflow or a dedicated state machine.
• UX matters — back-navigation, client-side validation, save-as-draft. That's a frontend step-component problem.
• Compliance or audit trails are in scope. An unmaintained dependency is a supply-chain finding, not a shortcut.

How to Pitch It (Stakeholders)

Executives: Not a strategic dependency. It's a small, low-signal package (0 stars, 0 dependents) that solves roughly a 1–3 day problem we can own ourselves. Recommend no adoption — treat it as a pattern reference, not a dependency.

Engineering: It's a Symfony bundle, filed here under Laravel/PHP — that mismatch is the first thing to correct. The step-per-controller-method + validation-gate pattern is reasonable to imitate, but the code itself is unmaintained and predates attribute routing. Reimplementing the pattern in either framework is a few days of work; forking and modernizing costs about the same plus ongoing ownership. Recommendation: build in-house or use the framework's native workflow tooling.