| name | feature-review |
| description | Feature review and prioritization with RICE/WSJF/Kano scoring. Creates GitHub issues for suggestions.
Triggers: feature review, prioritization, RICE, WSJF, roadmap, backlog
Use when: reviewing features or suggesting new features
DO NOT use when: evaluating single feature scope - use scope-guard.
|
| category | workflow-methodology |
| tags | ["feature-review","prioritization","RICE","WSJF","Kano","roadmap","backlog"] |
| dependencies | ["imbue:scope-guard","imbue:review-core"] |
| tools | ["gh (GitHub CLI)"] |
| usage_patterns | ["feature-inventory","prioritization-scoring","suggestion-generation","github-integration"] |
| complexity | intermediate |
| estimated_tokens | 3500 |
| modules | ["modules/scoring-framework.md","modules/classification-system.md","modules/tradeoff-dimensions.md","modules/configuration.md"] |
Feature Review
Review implemented features and suggest new ones using evidence-based prioritization. Create GitHub issues for accepted suggestions.
Philosophy
Core Belief: Feature decisions should be data-driven. Every feature has tradeoffs that deserve evaluation.
Three Pillars:
- Evidence-Based Scoring: Hybrid RICE+WSJF with Kano classification.
- Configurable Heuristics: Opinionated defaults with customization.
- Actionable Output: Issue generation for accepted features.
When to Use
- Periodic roadmap reviews (sprint planning, quarterly reviews).
- Retrospective evaluations after shipping features.
- Planning new development cycles.
When NOT to Use
- Emergency bug fixes.
- Simple documentation updates.
- Active implementation (use
scope-guard).
Quick Start
1. Inventory Current Features
Discover and categorize existing features:
/feature-review --inventory
2. Score and Classify
Evaluate features against the prioritization framework:
/feature-review
3. Generate Suggestions
Review gaps and suggest new features:
/feature-review --suggest
4. Upload to GitHub
Create issues for accepted suggestions:
/feature-review --suggest --create-issues
Workflow
Phase 1: Feature Discovery (feature-review:inventory-complete)
Identify features by analyzing:
- Code artifacts: Entry points, public APIs, and configuration surfaces.
- Documentation: README lists, CHANGELOG entries, and user docs.
- Git history: Recent feature commits and branches.
Output: Feature inventory table.
Phase 2: Classification (feature-review:classified)
Classify each feature along two axes:
Axis 1: Proactive vs Reactive
