- [Philosophy](#philosophy)
/plugin marketplace add athola/claude-night-market/plugin install imbue@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/classification-system.mdmodules/configuration.mdmodules/scoring-framework.mdmodules/tradeoff-dimensions.mdfeature-review:inventory-complete)feature-review:classified)feature-review:scored)feature-review:tradeoffs-analyzed)feature-review:suggestions-generated)feature-review:issues-created)Review implemented features and suggest new ones using evidence-based prioritization. Create GitHub issues for accepted suggestions.
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.
scope-guard).Discover and categorize existing features:
/feature-review --inventory
Evaluate features against the prioritization framework:
/feature-review
Review gaps and suggest new features:
/feature-review --suggest
Create issues for accepted suggestions:
/feature-review --suggest --create-issues
feature-review:inventory-complete)Identify features by analyzing:
Output: Feature inventory table.
feature-review:classified)Classify each feature along two axes:
Axis 1: Proactive vs Reactive
| Type | Definition | Examples |
|---|---|---|
| Proactive | Anticipates user needs. | Suggestions, prefetching. |
| Reactive | Responds to explicit input. | Form handling, click actions. |
Axis 2: Static vs Dynamic
| Type | Update Pattern | Storage Model |
|---|---|---|
| Static | Incremental, versioned. | File-based, cached. |
| Dynamic | Continuous, streaming. | Database, real-time. |
See classification-system.md for details.
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:
See scoring-framework.md for the framework.
feature-review:tradeoffs-analyzed)Evaluate each feature across quality dimensions:
| 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 |
See tradeoff-dimensions.md for criteria.
feature-review:suggestions-generated)feature-review:issues-created)Feature-review uses opinionated defaults but allows customization.
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.
These rules apply to all configurations:
feature-review:inventory-completefeature-review:classifiedfeature-review:scoredfeature-review:tradeoffs-analyzedfeature-review:suggestions-generatedfeature-review:issues-created (if requested)imbue:scope-guard: Provides Worthiness Scores for suggestions.sanctum:fix-issue: Prioritizes issues with high scores.superpowers:brainstorming: Evaluates new ideas against existing features.| 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 sprint
imbue:scope-guard: Prevent overengineering.imbue:review-core: Structured review methodology.sanctum:pr-review: Code-level feature review.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
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.