feat : add aem-agentify plugin

[rishabhdaim]

Summary

• Adds plugins/aem/agentify/ — a new AEM plugin that transforms any AEM customer repository into an AI-native one
• Covers all AEM repo types: OSGi bundles, content packages, multi-module Maven, AEM Cloud Service, and AEM 6.5/AMS projects
• Four-phase workflow: Assess → High-ROI wins → Contract clarity → Structural/automation
• review-governor referenced as an independent skill, not bundled — customers install it separately when needed
• Updates README.md with the new plugin entry and installation instructions

Why

AEM customers need a structured, guided way to make their custom bundle repos AI-native. This plugin provides a complete multi-phase workflow tailored to AEM conventions (OSGi, Sling, Maven, JUnit 4/5, even/odd versioning) without requiring customers to adapt a generic agentify skill.

Test Plan

• Verify plugin structure: plugins/aem/agentify/.claude-plugin/plugin.json exists and is valid
• Verify SKILL.md entry point loads correctly
• Verify no Adobe-internal references (GRANITE JIRAs, git.corp.adobe.com) remain in skill content
• Verify README.md plugin entry and installation block are correct

Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com

[trieloff]

@rombert can you take a look?

[rombert]

I think this goes a lot in the direction of #172 and has significat overlap with https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/ensure-agents-md .

We should pause and assess what we actually want to achieve with such initiatives and also make sure they are not too broad.

I am not a fan of giving context to the agent just because we can and I am actually starting to question the value of the ensure-agents-md skill now that we have fine-grained knowledge in specialist skills.

Let's please have a structured conversation about these initiatives to modernise the AEM projects, @rishabhdaim / @abhishekgarg18 - can one of you please create a GitHub issue here so we can agree on the goals and measurements?

Requesting changes so we don't accidentally merge this until we have consensus.

[trieloff]

Agree. Let's take this discussion back to Slack.

[rishabhdaim]

@trieloff @rombert how should we proceed here, GitHub issue or Slack?

[abhishekgarg18]

I am actually starting to question the value of the ensure-agents-md skill now that we have fine-grained knowledge in specialist skills.

Regarding this, I disagree with this point.
Specialist skills give you: generic, deep AEM knowledge , like how dispatcher config-authoring works, how workflow works etc, which gets loaded on-demand when the prompt matches. That knowledge is not repo-specific, it's true for every AEM Cloud Service repo.

What AGENTS.md/CLAUDE.md give you: repo-specific facts no skill can know, this repo's actual module layout, team's real conventions and anti-patterns, whether dispatcher/ even exists here. That doesn't become redundant just because specialist skills got better, because skills don't know this repo.

[rishabhdaim]

@trieloff @rombert @abhishekgarg18 taking the discussion back to slack.