From product-lens
Use when the system needs to judge recently built features or recent commit slices. Reviews whether recent work strengthens the core loop or creates drift.
npx claudepluginhub n0rvyn/indie-toolkit --plugin product-lensThis skill uses the workspace's default tool permissions.
`recent-feature-review` answers:
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides agent creation for Claude Code plugins with file templates, frontmatter specs (name, description, model), triggering examples, system prompts, and best practices.
recent-feature-review answers:
Use this only for already-built or recently changed work.
If the question is still "should we build this feature?", route to feature-assess.
{
"intent": "recent_feature_review",
"project_root": "~/Code",
"targets": ["~/Code/AppA"],
"window_days": 14,
"mode": "summary",
"save_report": true,
"sync_notion": false
}
Optional:
feature when the caller wants to constrain the review to one recent sliceUse explicit targets.
If missing, derive candidates from project_root.
For each target repository:
Dispatch feature-change-clusterer.
The clusterer should group recent changes into likely feature slices using:
For each slice, judge:
Allowed decision values:
double_downpolishsimplifyrethinkdropUse ingress-publisher with:
intent = recent_feature_reviewCommand shape:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/publish_exchange.py \
--intent recent_feature_review \
--project-root ~/Code \
--target ~/Code/AppA \
--project AppA \
--feature "tagging system" \
--window-days 14 \
--decision polish \
--confidence medium \
--risk "The feature is coherent, but it may expand too quickly into side workflows." \
--reason "Tagging strengthens note retrieval in the main workflow." \
--action "Polish the current tagging flow before adding automation." \
--evidence ~/Code/AppA/Sources/TaggingView.swift \
--exchange-root ~/Obsidian/PKOS/.exchange/product-lens
Exchange target:
~/Obsidian/PKOS/.exchange/product-lens/recent-feature-review/
Return the machine envelope first, then a compact report:
# Recent Feature Review
## Feature Slices
- Tagging — polish
- AI sidebar — rethink
## Core Loop Impact
- ...
## Recommended Follow-up
- ...