From magento2-tools
End-to-end Magento 2 feature implementation orchestrator (magento2-feature-implement)
How this command is triggered — by the user, by Claude, or both
Slash command
/magento2-tools:feature "<feature request>" | resume ./.docs/<FeatureName>The summary Claude sees in its command listing — used to decide when to auto-load this command
Use the `magento2-tools:magento2-feature-implement` skill, forwarding these arguments verbatim: $ARGUMENTS Do not bypass the blueprint or task-plan approval gates; the skill's normal flow applies.
Use the magento2-tools:magento2-feature-implement skill, forwarding these arguments verbatim: $ARGUMENTS
Do not bypass the blueprint or task-plan approval gates; the skill's normal flow applies.
npx claudepluginhub 5mehulhelp5/magento2-tools-muon-m22plugins reuse this command
First indexed Jul 5, 2026
/featureOrchestrates a complete feature development lifecycle covering product, architecture, development, QA, documentation, and delivery.
/featureCreates a new Git Flow feature branch from develop, validates naming and repository state, handles uncommitted changes, and pushes to remote with tracking.
/featureCreates a new feature or chore from issue URL or description, handling branch creation, implementation, testing, and PR readiness.
/featureCaptures a rough client requirement, drafts a PRD epic with scoped sub-issues, and pushes approved items to a GitHub Projects kanban.
/featureCreates a lightweight feature-focused PRD via guided interactive interview (5-8 rounds) optimized for new features in existing products, saving to docs/prd/{slug}.md
/featureExecutes Mermaid flowchart workflow: two Analyze-Design(D3)-Develop(G2→G2.5→G3)-Release cycles, using Task for sub-agents, AskUserQuestion at diamonds, and F5 gates.