Table of Contents

• •Philosophy
• •When to Use
• •When NOT to Use
• •Quick Start
• •1. Inventory Current Features
• •2. Score and Classify
• •3. Generate Suggestions

Verification

Run make test-feature-review to verify scoring logic after changes.

• •4. Upload to GitHub
• •Workflow
• •Phase 1: Feature Discovery (feature-review:inventory-complete)
• •Phase 2: Classification (feature-review:classified)
• •Phase 3: Scoring (feature-review:scored)
• •Phase 4: Tradeoff Analysis (feature-review:tradeoffs-analyzed)
• •Phase 5: Gap Analysis & Suggestions (feature-review:suggestions-generated)
• •Phase 6: GitHub Integration (feature-review:issues-created)
• •Configuration
• •Configuration File
• •Guardrails
• •Required TodoWrite Items
• •Integration Points
• •Output Format
• •Feature Inventory Table
• •Suggestion Report
• •Feature Suggestions
• •High Priority (Score > 2.5)
• •Related Skills
• •Reference

Feature Review

Review implemented features and suggest new ones using evidence-based prioritization. Create GitHub issues for accepted suggestions.

Philosophy

Feature decisions rely on data. Every feature involves tradeoffs that require evaluation. This skill uses hybrid RICE+WSJF scoring with Kano classification to prioritize work and generates actionable GitHub issues for accepted suggestions.

When To Use

• •Roadmap reviews (sprint planning, quarterly reviews).
• •Retrospective evaluations.
• •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:

1. •Code artifacts: Entry points, public APIs, and configuration surfaces.
2. •Documentation: README lists, CHANGELOG entries, and user docs.
3. •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

Axis 2: Static vs Dynamic

See classification-system.md for details.

Phase 3: Scoring (feature-review:scored)

Apply hybrid RICE+WSJF scoring:

Feature Score = Value Score / Cost Score

Value Score = (Reach + Impact + Business Value + Time Criticality) / 4
Cost Score = (Effort + Risk + Complexity) / 3

Adjusted Score = Feature Score * Confidence

Scoring Scale: Fibonacci (1, 2, 3, 5, 8, 13).

Thresholds:

• •> 2.5: High priority.
• •1.5 - 2.5: Medium priority.
• •< 1.5: Low priority.

See scoring-framework.md for the framework.

Phase 4: Tradeoff Analysis (feature-review:tradeoffs-analyzed)

Evaluate each feature across quality dimensions:

See tradeoff-dimensions.md for criteria.

Phase 5: Gap Analysis & Suggestions (feature-review:suggestions-generated)

1. •Identify gaps: Missing Kano basics.
2. •Surface opportunities: High-value, low-effort features.
3. •Flag technical debt: Features with declining scores.
4. •Recommend actions: Build, improve, deprecate, or maintain.

Phase 6: GitHub Integration (feature-review:issues-created)

1. •Generate issue title and body from suggestions.
2. •Apply labels (feature, enhancement, priority/*).
3. •Link to related issues.
4. •Confirm with user before creation.

Configuration

Feature-review uses opinionated defaults but allows customization.

Configuration File

Create .feature-review.yaml in project root:

# .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.0

See configuration.md for options.

Guardrails

These rules apply to all configurations:

1. •Minimum dimensions: Evaluate at least 5 tradeoff dimensions.
2. •Confidence requirement: Review scores below 50% confidence.
3. •Breaking change warning: Require acknowledgment for API surface changes.
4. •Backlog limit: Limit suggestion queue to 25 items.

Required TodoWrite Items

1. •feature-review:inventory-complete
2. •feature-review:classified
3. •feature-review:scored
4. •feature-review:tradeoffs-analyzed
5. •feature-review:suggestions-generated
6. •feature-review:issues-created (if requested)

Integration Points

• •imbue:scope-guard: Provides Worthiness Scores for suggestions.
• •sanctum:do-issue: Prioritizes issues with high scores.
• •superpowers:brainstorming: Evaluates new ideas against existing features.

Output Format

Feature Inventory Table

| Feature | Type | Data | Score | Priority | Status |
|---------|------|------|-------|----------|--------|
| Auth middleware | Reactive | Dynamic | 2.8 | High | Stable |
| Skill loader | Reactive | Static | 2.3 | Medium | Needs improvement |

Suggestion Report

## 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 sprint

Related Skills

• •imbue:scope-guard: Prevent overengineering.
• •imbue:review-core: Structured review methodology.
• •sanctum:pr-review: Code-level feature review.

Reference

• •scoring-framework.md: RICE+WSJF hybrid.
• •classification-system.md: Axes definition.
• •tradeoff-dimensions.md: Quality attributes.
• •configuration.md: Customization options.

Troubleshooting

Common Issues

Command not found Ensure all dependencies are installed and in PATH

Permission errors Check file permissions and run with appropriate privileges

Unexpected behavior Enable verbose logging with --verbose flag