Console Extra Laravel Package

Product Decisions This Supports

• Developer Productivity: Reduces boilerplate in Symfony CLI command development by 70-80% (via InvokableServiceCommand + attributes), accelerating feature delivery and reducing maintenance overhead.
• Consistent CLI UX: Enables standardized output formatting (e.g., success/error messages) and command summaries via IO and CommandSummarySubscriber, improving user experience.
• Modular Architecture: Supports attribute-based configuration (e.g., [AsCommand], [Argument]) for cleaner, more maintainable code, aligning with Symfony’s modern DI practices.
• Build vs. Buy: Buy for teams using Symfony 6.4+/PHP 8.1+; build only if needing custom CLI features beyond Symfony’s core (e.g., legacy systems or non-Symfony stacks).
• Use Cases:
  • Internal Tools: Rapidly develop admin/CLI tools (e.g., data migrations, user management).
  • DevOps Automation: Chain commands/processes (e.g., RunsCommands, RunsProcesses) for CI/CD pipelines.
  • Interactive Workflows: Simplify user prompts with IO and CommandRunner for scripts requiring input.

When to Consider This Package

• Adopt if:

  • Your team uses Symfony 6.4+ and PHP 8.1+ (required dependencies).
  • You’re writing >5 CLI commands and want to avoid repetitive Command boilerplate.
  • You need command chaining (e.g., running other commands/processes from within a command).
  • Your CLI tools require consistent styling (e.g., success/error messages) or performance metrics (e.g., execution time/memory).
  • You prefer attribute-based configuration over XML/YAML for commands.

• Look elsewhere if:

  • You’re not using Symfony (package is Symfony-specific).
  • Your CLI needs are simple (e.g., <5 commands with minimal dependencies).
  • You require legacy Symfony (<6.4) or PHP <8.1 support.
  • You need custom output formatting beyond Symfony’s StyleInterface.
  • Your team prefers XML/YAML over PHP attributes for configuration.

How to Pitch It (Stakeholders)

For Executives: "This package cuts CLI development time by 70% for Symfony apps, letting our team ship internal tools faster with less boilerplate. For example, a command to manage users now requires 3 lines of code instead of 30. It also standardizes output (e.g., success messages, performance metrics), reducing user errors and improving DevOps workflows. Low risk—MIT license, actively maintained, and used in production by [Zenstruck]."

For Engineers: *"Replace verbose Command classes with attribute-driven, service-injected commands using InvokableServiceCommand. Key wins:

• No execute() method: Just define __invoke() with type-hinted dependencies.
• Auto-wired services: Inject Symfony services (e.g., UserManager) like controllers.
• Command chaining: Run other commands/processes with $this->runCommand() or $this->runProcess().
• Consistent UX: Use IO for styled output and CommandSummarySubscriber for execution metrics. Example: A user-creation command drops from 50 to 10 lines of code. Works seamlessly with Symfony’s DI and attributes."*

For PMs: *"This aligns with our developer velocity and technical debt reduction goals. It’s a low-effort, high-impact upgrade for CLI-heavy projects (e.g., migrations, admin tools). Prioritize if:

• Your roadmap includes internal tooling (e.g., data pipelines).
• Devs spend >20% of CLI dev time on boilerplate.
• You want to standardize CLI output across teams."*