fix(agile-product-owner): add standalone plugin.json + marketplace entry

[alirezarezvani]

Summary

• Adds standalone .claude-plugin/plugin.json so the skill can be installed individually via /plugin install agile-product-owner@claude-code-skills
• Adds marketplace entry (36th plugin, category: product)

Previously, agile-product-owner was only available as part of the product-skills domain bundle. Now it's also installable as a standalone plugin.

Follow-up to PR #521 which improved the skill's frontmatter (not_for boundaries, triggers, differentiators section).

Cross-tool availability

Platform	Status
Claude Code (standalone)	✅ NEW — plugin.json + marketplace entry
Claude Code (bundle)	✅ already in product-skills bundle
Codex CLI	✅ in skills-index.json
Gemini CLI	✅ in skills-index.json
Hermes Agent	✅ discoverable via sync-hermes-skills.py
Top-level agent	✅ agents/product/cs-agile-product-owner.md

Security

Audit: PASS (0 critical, 0 high)

Test plan

• plugin.json valid JSON, only allowed fields
• marketplace.json valid JSON (36 plugins, 0 missing sources)
• Codex/Gemini/Hermes sync scripts confirm presence
• user_story_generator.py --help passes

🤖 Generated with Claude Code

[claude]

Code Review — PR #531: fix(agile-product-owner): add standalone plugin.json + marketplace entry

Note: PR is already merged. This review is for record-keeping and future reference.

---

Summary

This PR adds standalone installability for the agile-product-owner skill by introducing a plugin.json file and a marketplace entry. The change is additive only (new file + 1 new array element in JSON), no existing behaviour is modified.

---

✅ What's Good

• JSON validity — both files are well-formed and parse correctly.
• Version alignment — version: "2.3.0" matches the current repo release in CLAUDE.md and other recent plugin entries (karpathy-coder, llm-wiki).
• Structure consistency — plugin.json mirrors the pattern established by apple-hig-expert and code-to-prd: same field order, same author.url inclusion, same skills: "./" value.
• Category correctness — "category": "product" is appropriate and consistent with the domain.
• Keywords — 8 relevant, lowercase-kebab keywords that accurately reflect the skill's capabilities.
• PR description quality — cross-tool availability matrix and test checklist are thorough.

---

⚠️ Minor Issues

1. Description drift between plugin.json and marketplace.json

plugin.json description ends with:

"Includes user_story_generator Python tool."

marketplace.json description ends with:

"Includes user_story_generator Python tool and 2 reference guides."

The marketplace entry is more accurate. The plugin.json description should mention the reference guides for completeness. Low severity — both are truthful, just uneven.

2. author.url not in CLAUDE.md's allowed field list

CLAUDE.md states plugin.json ONLY allows: name, description, version, author, homepage, repository, license, skills. The author.url sub-field isn't listed. However, this is already present in apple-hig-expert, code-to-prd, and other established plugins — so this PR is simply following existing convention. The CLAUDE.md constraint may be outdated or under-specified. Worth documenting the accepted pattern explicitly.

3. marketplace.json entry lacks author.url

The plugin.json has "author": { "name": "...", "url": "..." } but the marketplace entry only has "author": { "name": "..." }. This is consistent with all other marketplace entries (none include author.url there), so it's not a regression — but the inconsistency within the same PR is worth noting.

---

🔍 Schema Validation

Check	Result
plugin.json is valid JSON	✅
Only allowed fields present (name, description, version, author, homepage, repository, license, skills)	✅ (plus author.url, established pattern)
skills: "./" present	✅
marketplace.json is valid JSON	✅
New entry has required fields (name, source, description, version, author, keywords, category)	✅
source path points to existing directory	✅ ./product-team/agile-product-owner
Version matches repo release	✅ 2.3.0

---

🚫 No Issues Found

• No security concerns (static JSON metadata only)
• No breaking changes
• No logic or script modifications
• No Python syntax issues (scripts untouched)

---

Recommendation

Approve. The PR is clean, consistent, and low-risk. Two optional follow-ups for a future PR:

1. Align plugin.json description to include "and 2 reference guides" (matches marketplace entry)
2. Update CLAUDE.md's plugin.json schema note to explicitly permit author.url as an optional sub-field, since it's already in widespread use.

🤖 Reviewed by Claude Code