Compare competing customer use cases by value, feasibility and evidence. Use when several problems compete for delivery capacity.
Pro scans all 6 files and shows the line behind each finding
Scanned 10/6/2026
npx -y skills add suboss87/FDEOps --skill score-use-cases --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Score Use Cases?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/suboss87-score-use-cases)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: score-use-cases
description: Compare competing customer use cases by value, feasibility and evidence. Use when several problems compete for delivery capacity.
---
# score-use-cases
<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->
## Purpose
A ranked use-case shortlist with evidence and trade-offs.
Before investigating or acting:
1. Read [the task context contract](references/task-context.md).
2. Read [the method](references/score-use-cases.md).
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
## Principles
- Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
- If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
- The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
- Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!