Loading...
Loading...
Feature review and prioritization with RICE/WSJF/Kano scoring. Creates GitHub issues for suggestions. 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.
npx skill4agent add athola/claude-night-market feature-reviewmake test-feature-reviewfeature-review:inventory-completefeature-review:classifiedfeature-review:scoredfeature-review:tradeoffs-analyzedfeature-review:suggestions-generatedfeature-review:issues-createdscope-guard/feature-review --inventory/feature-review/feature-review --suggest/feature-review --suggest --create-issuesfeature-review:inventory-completefeature-review:classified| Type | Definition | Examples |
|---|---|---|
| Proactive | Anticipates user needs. | Suggestions, prefetching. |
| Reactive | Responds to explicit input. | Form handling, click actions. |
| Type | Update Pattern | Storage Model |
|---|---|---|
| Static | Incremental, versioned. | File-based, cached. |
| Dynamic | Continuous, streaming. | Database, real-time. |
feature-review:scoredFeature Score = Value Score / Cost Score
Value Score = (Reach + Impact + Business Value + Time Criticality) / 4
Cost Score = (Effort + Risk + Complexity) / 3
Adjusted Score = Feature Score * Confidencefeature-review:tradeoffs-analyzed| Dimension | Question | Scale |
|---|---|---|
| Quality | Does it deliver correct results? | 1-5 |
| Latency | Does it meet timing requirements? | 1-5 |
| Token Usage | Is it context-efficient? | 1-5 |
| Resource Usage | Is CPU/memory reasonable? | 1-5 |
| Redundancy | Does it handle failures gracefully? | 1-5 |
| Readability | Can others understand it? | 1-5 |
| Scalability | Will it handle 10x load? | 1-5 |
| Integration | Does it play well with others? | 1-5 |
| API Surface | Is it backward compatible? | 1-5 |
feature-review:suggestions-generatedfeature-review:issues-created.feature-review.yaml# .feature-review.yaml
version: 1
# Scoring weights (must sum to 1.0)
weights:
value:
reach: 0.25
impact: 0.30
business_value: 0.25
time_criticality: 0.20
cost:
effort: 0.40
risk: 0.30
complexity: 0.30
# Score thresholds
thresholds:
high_priority: 2.5
medium_priority: 1.5
# Tradeoff dimension weights (0.0 to disable)
tradeoffs:
quality: 1.0
latency: 1.0
token_usage: 1.0
resource_usage: 0.8
redundancy: 0.5
readability: 1.0
scalability: 0.8
integration: 1.0
api_surface: 1.0feature-review:inventory-completefeature-review:classifiedfeature-review:scoredfeature-review:tradeoffs-analyzedfeature-review:suggestions-generatedfeature-review:issues-createdimbue:scope-guardsanctum:do-issuesuperpowers:brainstorming| Feature | Type | Data | Score | Priority | Status |
|---------|------|------|-------|----------|--------|
| Auth middleware | Reactive | Dynamic | 2.8 | High | Stable |
| Skill loader | Reactive | Static | 2.3 | Medium | Needs improvement |## Feature Suggestions
### High Priority (Score > 2.5)
1. **[Feature Name]** (Score: 2.7)
- Classification: Proactive/Dynamic
- Value: High reach
- Cost: Moderate effort
- Recommendation: Build in next sprintimbue:scope-guardimbue:review-coresanctum:pr-review--verbose