Perform structured critical assessment of a proposal or approach
Evaluates proposals against correctness, architecture, alternatives, and risks before implementation.
/plugin marketplace add flexion/claude-domestique/plugin install mantra@claude-domestiqueproposal or contextPerform a structured evaluation of a proposal, approach, or solution before implementation.
IMPORTANT: This skill implements the CRITICAL ASSESSMENT rule from behavior.md
When the user presents a proposal, solution, or asks for agreement on an approach, you MUST assess before agreeing.
Evaluate these dimensions in order:
Correctness
Architecture
Alternatives
Risks
Structure your response as:
## Assessment: [proposal summary]
### Correctness
[findings]
### Architecture
[findings]
### Alternatives
[findings]
### Risks
[findings]
### Recommendation
[approve/revise/reject with reasoning]
User: /mantra:assess I think we should add a caching layer using Redis for all API responses
Claude: ## Assessment: Add Redis caching for all API responses
### Correctness
The goal of improving response times is valid, but "all API responses" is too broad. Some endpoints (user profile, real-time data) shouldn't be cached.
### Architecture
Adding Redis creates a new infrastructure dependency. Current architecture uses in-memory caching for specific endpoints. Mixing approaches may create inconsistency.
### Alternatives
1. **Expand existing in-memory caching** - simpler, no new deps
2. **CDN edge caching** - better for static/semi-static responses
3. **Selective Redis** - only for specific expensive queries
### Risks
- Cache invalidation complexity
- Redis availability becomes critical path
- Memory costs for unused cached data
- Cold start problems after Redis restart
### Recommendation
**Revise**: Start with selective caching for identified slow endpoints. Measure before adding infrastructure complexity. Consider: which specific endpoints are slow? What's the current p99 latency?
Invoke this skill when: